| Message ID | 20220720230140.2113129-1-bjorn.andersson@linaro.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [GIT,PULL] Qualcomm ARM64 defconfig more updates for v5.20 | expand |
On Wed, Jul 20, 2022 at 6:01 PM Bjorn Andersson <bjorn.andersson@linaro.org> wrote: > I don't seem to have received a response on this one, can you confirm if you were able to pick it up for v5.20? Thanks, Bjorn > The following changes since commit 76f11e77f919397f31198354cd0e0bd8e76f8748: > > arm64: defconfig: enable Qualcomm Bandwidth Monitor (2022-07-06 15:58:13 -0500) > > are available in the Git repository at: > > https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/qcom-arm64-defconfig-for-5.20-2 > > for you to fetch changes up to 01579b88a03a90af73b584fed70d171c73c2c540: > > arm64: defconfig: Demote Qualcomm USB PHYs to modules (2022-07-18 18:56:02 -0500) > > ---------------------------------------------------------------- > Qualcomm ARM64 defconfig more updates for v5.20 > > This enables a few of the core drivers needed to boot the 8cx Gen 3 > platform and demotes the Qualcomm USB PHY drivers to modules, as they > don't need to be builtin. > > ---------------------------------------------------------------- > Bjorn Andersson (2): > arm64: defconfig: Enable Qualcomm SC8280XP providers > arm64: defconfig: Demote Qualcomm USB PHYs to modules > > arch/arm64/configs/defconfig | 11 +++++++---- > 1 file changed, 7 insertions(+), 4 deletions(-)
On Mon, Aug 1, 2022 at 5:35 AM Bjorn Andersson <bjorn.andersson@linaro.org> wrote: > > On Wed, Jul 20, 2022 at 6:01 PM Bjorn Andersson > <bjorn.andersson@linaro.org> wrote: > > > > I don't seem to have received a response on this one, can you confirm > if you were able to pick it up for v5.20? Hi Bjorn, sorry I missed sending out an email. For some reason the automatic notifications don't work for some senders and I have to manually chase those up. You can always see what I actually merged when looking at the arch/arm/arm-soc-for-next-contents.txt file in my for-next branch, which is also part of linux-next. Arnd
On Tue, Aug 02, 2022 at 11:44:16AM +0200, Arnd Bergmann wrote: > On Mon, Aug 1, 2022 at 5:35 AM Bjorn Andersson > <bjorn.andersson@linaro.org> wrote: > > > > On Wed, Jul 20, 2022 at 6:01 PM Bjorn Andersson > > <bjorn.andersson@linaro.org> wrote: > > > > > > > I don't seem to have received a response on this one, can you confirm > > if you were able to pick it up for v5.20? > > Hi Bjorn, > > sorry I missed sending out an email. For some reason the automatic notifications > don't work for some senders and I have to manually chase those up. > Ah that explains why I didn't receive notification as well. I noticed the changes were pulled. I didn't bother to ask, but now that you mention it is likely to be the sender address as I can't send you email to your @arndb.de and hence I always use kernel.org. Are these automated emails sent via arnd@arndb.de ? -- Regards, Sudeep
On Tue, Aug 2, 2022 at 11:53 AM Sudeep Holla <sudeep.holla@arm.com> wrote: > On Tue, Aug 02, 2022 at 11:44:16AM +0200, Arnd Bergmann wrote: > > On Mon, Aug 1, 2022 at 5:35 AM Bjorn Andersson > > <bjorn.andersson@linaro.org> wrote: > > > > > > On Wed, Jul 20, 2022 at 6:01 PM Bjorn Andersson > > > <bjorn.andersson@linaro.org> wrote: > > > > > > > > > > I don't seem to have received a response on this one, can you confirm > > > if you were able to pick it up for v5.20? > > > > Hi Bjorn, > > > > sorry I missed sending out an email. For some reason the automatic notifications > > don't work for some senders and I have to manually chase those up. > > > > Ah that explains why I didn't receive notification as well. I noticed > the changes were pulled. I didn't bother to ask, but now that you mention > it is likely to be the sender address as I can't send you email to your > @arndb.de and hence I always use kernel.org. Are these automated emails > sent via arnd@arndb.de ? I don't think it has anything to do with my email address. This is about pull requests that get sent to the soc@kernel.org alias. Patchwork monitors these and puts them into https://patchwork.kernel.org/project/linux-soc/list/ from where I can pick them up or reject them using pwclient. Anything sent there requires an action to get it out of the list of 'New' entries. In most cases patchwork will then notice when I push out the merge commit to the for-next branch of the soc tree. However for some senders (Bjorn and Krzysztof notably), this only works for patch emails but not pull requests, so I have to use 'b4' to to send an 'applied, thanks' message myself, which I send using gmail with my kernel.org address as sender. Arnd
On Tue, Aug 02, 2022 at 12:22:33PM +0200, Arnd Bergmann wrote: > On Tue, Aug 2, 2022 at 11:53 AM Sudeep Holla <sudeep.holla@arm.com> wrote: [...] > > Ah that explains why I didn't receive notification as well. I noticed > > the changes were pulled. I didn't bother to ask, but now that you mention > > it is likely to be the sender address as I can't send you email to your > > @arndb.de and hence I always use kernel.org. Are these automated emails > > sent via arnd@arndb.de ? > > I don't think it has anything to do with my email address. This is about pull > requests that get sent to the soc@kernel.org alias. Patchwork monitors these > and puts them into https://patchwork.kernel.org/project/linux-soc/list/ from > where I can pick them up or reject them using pwclient. Anything sent there > requires an action to get it out of the list of 'New' entries. > > In most cases patchwork will then notice when I push out the merge commit > to the for-next branch of the soc tree. However for some senders (Bjorn and > Krzysztof notably), this only works for patch emails but not pull requests, so > I have to use 'b4' to to send an 'applied, thanks' message myself, which I send > using gmail with my kernel.org address as sender. > Thanks for the details. I have received those automated "merged" emails in the past for sure(e.g. my PR for v5.19) but I didn't get this time(PRs for v5.20). I assumed it wasn't working that day as I didn't see emails for other PRs that got merged more or less at the same time. Anyways I have soc tree as remote and generally check the contents of next especially if I have pending PR, so I don't rely much on the emails. -- Regards, Sudeep
The following changes since commit 76f11e77f919397f31198354cd0e0bd8e76f8748: arm64: defconfig: enable Qualcomm Bandwidth Monitor (2022-07-06 15:58:13 -0500) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git tags/qcom-arm64-defconfig-for-5.20-2 for you to fetch changes up to 01579b88a03a90af73b584fed70d171c73c2c540: arm64: defconfig: Demote Qualcomm USB PHYs to modules (2022-07-18 18:56:02 -0500) ---------------------------------------------------------------- Qualcomm ARM64 defconfig more updates for v5.20 This enables a few of the core drivers needed to boot the 8cx Gen 3 platform and demotes the Qualcomm USB PHY drivers to modules, as they don't need to be builtin. ---------------------------------------------------------------- Bjorn Andersson (2): arm64: defconfig: Enable Qualcomm SC8280XP providers arm64: defconfig: Demote Qualcomm USB PHYs to modules arch/arm64/configs/defconfig | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)