From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Greg KH <greg@kroah.com>, Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
William Zhang <william.zhang@broadcom.com>,
ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: linux-next: manual merge of the broadcom tree with the spdx tree
Date: Thu, 14 Jul 2022 14:10:19 +1000 [thread overview]
Message-ID: <20220714141019.43b45f68@canb.auug.org.au> (raw)
In-Reply-To: <8a37363d-f4d9-669c-9cc6-3e76b9417352@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 436 bytes --]
Hi Florian,
On Wed, 13 Jul 2022 16:26:33 -0700 Florian Fainelli <f.fainelli@gmail.com> wrote:
>
> There was a link in the cover letter that I sent to the arm-soc
> maintainers referencing your first email. Not sure what else we could
> have done to prevent that conflict.
Nothing really. Hopefully between the 2 notifications, the arm-soc and
spdx guys will remember to let Linus know ...
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-14 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220711095520.4fad4c97@canb.auug.org.au>
2022-07-13 23:13 ` linux-next: manual merge of the broadcom tree with the spdx tree Stephen Rothwell
2022-07-13 23:26 ` Florian Fainelli
2022-07-14 4:10 ` Stephen Rothwell [this message]
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=20220714141019.43b45f68@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tglx@linutronix.de \
--cc=william.zhang@broadcom.com \
/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