From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Arnd Bergmann <arnd@kernel.org>, Conor Dooley <mail@conchuod.ie>
Cc: Lewis Hanly <lewis.hanly@microchip.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Conor Dooley <conor.dooley@microchip.com>,
Arnd Bergmann <arnd@arndb.de>,
"kernel test robot" <lkp@intel.com>,
Jassi Brar <jaswinder.singh@linaro.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<llvm@lists.linux.dev>
Subject: Re: [PATCH] SoC: polarfire: fix build warning
Date: Mon, 28 Feb 2022 17:09:50 +0100 [thread overview]
Message-ID: <3fedb4c6-baa5-2107-934d-31f8205176b4@microchip.com> (raw)
In-Reply-To: <CAK8P3a1NWuoHVWXVZUGJxSg=D0d3umrMzWqZ75devfOwO-JhuQ@mail.gmail.com>
On 28/02/2022 at 16:41, Arnd Bergmann wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Mon, Feb 28, 2022 at 4:35 PM Conor Dooley <mail@conchuod.ie> wrote:
>>
>> I had sent a fix for the build warning on saturday morning - but I guess
>> you missed it.
>>
>> Thanks for fixing it anyway :)
>
> Thank you for your quick reply. I had indeed missed that fix. You did the
> right thing here by sending it to Nicolas, but he hasn't had a chance to forward
> it to soc@kernel.org yet, so it was not visible in patchwork.
>
> As it turns out, your patch is correct and mine was wrong anyway, so I
> have now replaced my patch with yours.
>
> Nicolas, I hope that doesn't cause you extra work. If you have picked it
> up into your tree, you can drop it again from there.
No problem on my side: I was planning to add it to another PR to you but
it's far easier if you already took it directly.
Thanks Arnd, best regards,
Nicolas
--
Nicolas Ferre
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-02-28 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 15:26 [PATCH] SoC: polarfire: fix build warning Arnd Bergmann
2022-02-28 15:35 ` Conor Dooley
2022-02-28 15:41 ` Arnd Bergmann
2022-02-28 16:09 ` Nicolas Ferre [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=3fedb4c6-baa5-2107-934d-31f8205176b4@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=jaswinder.singh@linaro.org \
--cc=lewis.hanly@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mail@conchuod.ie \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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