From: Sudeep Holla <sudeep.holla@arm.com> To: Arnd Bergmann <arnd@kernel.org> Cc: Olof Johansson <olof@lixom.net>, ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>, Sudeep Holla <sudeep.holla@arm.com>, ALKML <linux-arm-kernel@lists.infradead.org>, Cristian Marussi <cristian.marussi@arm.com> Subject: Re: [GIT PULL] firmware: arm_scmi: Updates for v5.17 Date: Tue, 8 Feb 2022 10:33:27 +0000 [thread overview] Message-ID: <20220208103327.hjld33z3lkfrpu6k@bogus> (raw) In-Reply-To: <CAK8P3a1qcZHFpxdqF1AFSCGR+AyDrYmucdBQGz5G1PvnEMbp8Q@mail.gmail.com> On Tue, Feb 08, 2022 at 11:00:43AM +0100, Arnd Bergmann wrote: > On Sat, Jan 8, 2022 at 9:24 PM Olof Johansson <olof@lixom.net> wrote: > > On Fri, Jan 07, 2022 at 11:37:40AM +0000, Sudeep Holla wrote: > > > On Wed, Dec 22, 2021 at 02:13:42PM +0000, Sudeep Holla wrote: > > > > Hi ARM SoC Team, > > > > > > > > Please pull ! > > > > > > > > > > I am aware I sent this pull request just around the same time Arnd finalised > > > the initial set. I have seen emails suggesting that Olof might be planning > > > to merge additional PR, so it would be great if this gets included in > > > that cut. All the changes are in -next since 21st December, so there should > > > be no surprises. > > > > > > Thanks again and sorry for nagging. > > > > Yeah, no worries -- I'd been letting pull requests sitting for a while over the > > holidays. I've merged this into our late branch now. > > Hi Sudeep, > > I'm going through all the stuff that we ended up not getting into v5.17. > As you probably already know, this pull request was part of the arm/late > branch that missed out, sorry for the mistake on our end. > No worries, it was indeed a late PR. > As the contents are still fine, I could offer to either merge the branch again > for v5.18, or I can drop it and wait for a new pull request from you, please > let me know your preference. > Is it OK if I merge this tag with v5.17-rc1 as base and load it with any new v5.18 material on the top ? I just want to avoid rebasing as the same time some of the new material depend on these changes. Let me know if that is fine. I am open to any other suggestions too. > If any of the patches are bug fixes that you think should be in v5.17, > it would be good to have a separate pull request or patch email for the > 5.17 fixes branch. > Sure, I will check again, but AFAIK there were no fixes for existing bugs. -- Regards, Sudeep
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com> To: Arnd Bergmann <arnd@kernel.org> Cc: Olof Johansson <olof@lixom.net>, ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>, Sudeep Holla <sudeep.holla@arm.com>, ALKML <linux-arm-kernel@lists.infradead.org>, Cristian Marussi <cristian.marussi@arm.com> Subject: Re: [GIT PULL] firmware: arm_scmi: Updates for v5.17 Date: Tue, 8 Feb 2022 10:33:27 +0000 [thread overview] Message-ID: <20220208103327.hjld33z3lkfrpu6k@bogus> (raw) In-Reply-To: <CAK8P3a1qcZHFpxdqF1AFSCGR+AyDrYmucdBQGz5G1PvnEMbp8Q@mail.gmail.com> On Tue, Feb 08, 2022 at 11:00:43AM +0100, Arnd Bergmann wrote: > On Sat, Jan 8, 2022 at 9:24 PM Olof Johansson <olof@lixom.net> wrote: > > On Fri, Jan 07, 2022 at 11:37:40AM +0000, Sudeep Holla wrote: > > > On Wed, Dec 22, 2021 at 02:13:42PM +0000, Sudeep Holla wrote: > > > > Hi ARM SoC Team, > > > > > > > > Please pull ! > > > > > > > > > > I am aware I sent this pull request just around the same time Arnd finalised > > > the initial set. I have seen emails suggesting that Olof might be planning > > > to merge additional PR, so it would be great if this gets included in > > > that cut. All the changes are in -next since 21st December, so there should > > > be no surprises. > > > > > > Thanks again and sorry for nagging. > > > > Yeah, no worries -- I'd been letting pull requests sitting for a while over the > > holidays. I've merged this into our late branch now. > > Hi Sudeep, > > I'm going through all the stuff that we ended up not getting into v5.17. > As you probably already know, this pull request was part of the arm/late > branch that missed out, sorry for the mistake on our end. > No worries, it was indeed a late PR. > As the contents are still fine, I could offer to either merge the branch again > for v5.18, or I can drop it and wait for a new pull request from you, please > let me know your preference. > Is it OK if I merge this tag with v5.17-rc1 as base and load it with any new v5.18 material on the top ? I just want to avoid rebasing as the same time some of the new material depend on these changes. Let me know if that is fine. I am open to any other suggestions too. > If any of the patches are bug fixes that you think should be in v5.17, > it would be good to have a separate pull request or patch email for the > 5.17 fixes branch. > Sure, I will check again, but AFAIK there were no fixes for existing bugs. -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-08 10:34 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-22 14:13 [GIT PULL] firmware: arm_scmi: Updates for v5.17 Sudeep Holla 2021-12-22 14:13 ` Sudeep Holla 2022-01-07 11:37 ` Sudeep Holla 2022-01-07 11:37 ` Sudeep Holla 2022-01-08 20:24 ` Olof Johansson 2022-01-08 20:24 ` Olof Johansson 2022-02-08 10:00 ` Arnd Bergmann 2022-02-08 10:00 ` Arnd Bergmann 2022-02-08 10:33 ` Sudeep Holla [this message] 2022-02-08 10:33 ` Sudeep Holla 2022-02-08 11:14 ` Arnd Bergmann 2022-02-08 11:14 ` Arnd Bergmann 2022-02-08 11:34 ` Sudeep Holla 2022-02-08 11:34 ` Sudeep Holla 2022-01-08 22:00 ` patchwork-bot+linux-soc
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220208103327.hjld33z3lkfrpu6k@bogus \ --to=sudeep.holla@arm.com \ --cc=arm@kernel.org \ --cc=arnd@kernel.org \ --cc=cristian.marussi@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=olof@lixom.net \ --cc=soc@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.