From: Tanmay Shah <tanmays@amd.com>
To: Arnd Bergmann <arnd@arndb.de>, Arnd Bergmann <arnd@kernel.org>,
Michal Simek <michal.simek@xilinx.com>
Cc: soc@kernel.org, Tanmay Shah <tanmay.shah@xilinx.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Ben Levinsky <ben.levinsky@amd.com>,
Ronak Jain <ronak.jain@xilinx.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: zynqmp: fix declarations for gcc-13
Date: Tue, 17 Jan 2023 12:14:56 -0800 [thread overview]
Message-ID: <976dc694-5828-9975-8e87-ac0a850f75d0@amd.com> (raw)
In-Reply-To: <eec4d2fd-f305-452a-a47f-83203da494df@app.fastmail.com>
On 1/17/23 12:03 PM, Arnd Bergmann wrote:
> On Tue, Jan 17, 2023, at 20:53, Tanmay Shah wrote:
>> This looks good to me. Thanks for fixing this.
>>
>> Something must have gone wrong when I ran sparse check on this patch.
> I don't think any of our previous tooling caught this, only gcc-13
> changed some of the behavior around enums.
>
>> Just one question, does this patch need "fixes:" tag?
> Probably a good idea:
>
> Fixes: a5e56980cfb7 ("firmware: xilinx: Add RPU configuration APIs")
>
> I can apply this directly to the soc fixes branch if you like
> and add that line.
>
> Arnd
I am ok with that.
Thanks,
Tanmay
_______________________________________________
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:[~2023-01-17 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 16:41 [PATCH] firmware: zynqmp: fix declarations for gcc-13 Arnd Bergmann
2023-01-17 19:53 ` Tanmay Shah
2023-01-17 20:03 ` Arnd Bergmann
2023-01-17 20:14 ` Tanmay Shah [this message]
2023-01-18 7:29 ` Michal Simek
2023-01-18 7:31 ` Arnd Bergmann
2023-01-18 7:38 ` Michal Simek
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=976dc694-5828-9975-8e87-ac0a850f75d0@amd.com \
--to=tanmays@amd.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=ben.levinsky@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=michal.simek@xilinx.com \
--cc=ronak.jain@xilinx.com \
--cc=soc@kernel.org \
--cc=tanmay.shah@xilinx.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;
as well as URLs for NNTP newsgroup(s).