From: Florian Fainelli <f.fainelli@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: soc@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ARM: SoC fixes for 6.0-rc6
Date: Thu, 22 Sep 2022 14:23:08 -0700 [thread overview]
Message-ID: <438db2a8-0b41-23b4-a369-4475bea90795@gmail.com> (raw)
In-Reply-To: <79fed88c-7dae-4131-a005-b8374b5fe660@www.fastmail.com>
On 9/22/22 14:22, Arnd Bergmann wrote:
> On Thu, Sep 22, 2022, at 8:17 PM, Florian Fainelli wrote:
>> On 9/22/22 11:13, Linus Torvalds wrote:
>>> I could pull your Broadcom fixes directly on top if you/Arnd would
>>> prefer that as a solution?
>>
>> Thanks for the offer, no real urgency on my side, if there is a -rc7,
>> maybe Arnd can submit a follow up for ARM SoC fixes, as there is a good
>> chance we will accumulate more of those between -rc6 and then. If not,
>> and Arnd is fine with it, yes please pull mine directly, thanks!
>
> Yes, that was my plan already, sorry for not making that clearer already:
>
> I still have a couple of fixes pull requests in a backlog, including
> yours. Since the fixes branch was already large and the rest has
> not been in my tree yet, I decided to send whatever I had already,
> but planned to pick the rest up tomorrow morning to send early next
> week after I get a successful test result from the build bots.
Works for me, thanks!
--
Florian
next prev parent reply other threads:[~2022-09-22 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 15:32 [GIT PULL] ARM: SoC fixes for 6.0-rc6 Arnd Bergmann
2022-09-22 17:19 ` Florian Fainelli
2022-09-22 18:13 ` Linus Torvalds
2022-09-22 18:17 ` Florian Fainelli
2022-09-22 21:22 ` Arnd Bergmann
2022-09-22 21:23 ` Florian Fainelli [this message]
2022-09-22 18:15 ` pr-tracker-bot
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=438db2a8-0b41-23b4-a369-4475bea90795@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=torvalds@linux-foundation.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).