[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221025115214.26a12211@kernel.org>
Date: Tue, 25 Oct 2022 11:52:14 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: kernel test robot <lkp@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
ntfs3@...ts.linux.dev, netdev@...r.kernel.org,
linux-parisc@...r.kernel.org, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
amd-gfx@...ts.freedesktop.org,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: [linux-next:master] BUILD SUCCESS WITH WARNING
76cf65d1377f733af1e2a55233e3353ffa577f54
On Tue, 25 Oct 2022 09:21:07 +0100 Russell King (Oracle) wrote:
> Not me, Sean. My original implementation of phylink_validate_mask_caps()
> doesn't know anything about rate matching, so my version didn't have
> this issue.
>
> Sean's version of my patch (which is what was submitted) added the
> dereference that causes this, so, it's up to Sean to figure out a fix -
> but he reading his follow up to the build bot's message, he seems to
> be passing it over to me to fix!
>
> I've got other issues to be worked on right now, and have no time to
> spare to fix other people's mistakes. Sorry.
>
> You can't always rely on the apparent author mentioned in the commit to
> be the actual person responsible for the changes in a patch.
Eh, confusing authorship trail, sorry.
I'll send a patch to drop the if (), if it's really needed we'll hear
about it sooner or later.
Powered by blists - more mailing lists