From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Raju Rangoju <Raju.Rangoju@amd.com>,
Nathan Chancellor <nathan@kernel.org>,
linux-spi@vger.kernel.org, llvm@lists.linux.dev,
patches@lists.linux.dev, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] spi: amd: Fix -Wuninitialized in amd_spi_exec_mem_op()
Date: Wed, 15 Jan 2025 19:30:14 +0100 [thread overview]
Message-ID: <874j20nd55.fsf@bootlin.com> (raw)
In-Reply-To: <a20383dd-57cc-4c0d-8bab-09a9260f2378@sirena.org.uk> (Mark Brown's message of "Tue, 14 Jan 2025 15:17:59 +0000")
>> I'm wondering whether it's relevant to pull the branch you shared
>> as-is. Do you plan on pushing this patch of top of it? Or shall I wait
>> -rc1 for the SPI NAND part?
>
> Well, it's not a branch but rather a tag which complicates matters a
> bit. I could cherry pick the patch over and make a new tag I guess? Or
> you could just not do allmodconfig builds with clang?
I'm worried about the others, if Linus happens to pull my tree before
yours :) I don't specifically use clang :)
> for you to fetch changes up to e896c04890aeff2292364c19632fc15d890d436c:
>
> spi: amd: Fix -Wuninitialized in amd_spi_exec_mem_op() (2025-01-14
> 15:07:11 +0000)
Pulled into nand/next. Thanks a lot!
Miquèl
prev parent reply other threads:[~2025-01-15 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 19:08 [PATCH] spi: amd: Fix -Wuninitialized in amd_spi_exec_mem_op() Nathan Chancellor
2025-01-11 19:27 ` Miguel Ojeda
2025-01-13 10:42 ` Miquel Raynal
2025-01-13 16:45 ` Mark Brown
2025-01-14 10:03 ` Miquel Raynal
2025-01-14 15:17 ` Mark Brown
2025-01-15 18:30 ` Miquel Raynal [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=874j20nd55.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Raju.Rangoju@amd.com \
--cc=broonie@kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
/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