From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
kernel test robot <lkp@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7646/8170] arch/powerpc/kexec/crash.c:488:2-8: WARNING: NULL check before some freeing functions is not needed.
Date: Fri, 3 May 2024 00:01:33 +0530 [thread overview]
Message-ID: <dbc992da-ffa3-4d62-9e0c-734e9d180fec@linux.ibm.com> (raw)
In-Reply-To: <87o79o2vqc.fsf@mail.lhotse>
Hello Michael and Stephen,
On 02/05/24 18:53, Michael Ellerman wrote:
> Sourabh Jain <sourabhjain@linux.ibm.com> writes:
>> Hello Michael and Stephen,
>>
>> I fixed the below build warning in v19:
>>
>> v19 patch series link:
>> https://lore.kernel.org/all/20240426060728.559753-1-sourabhjain@linux.ibm.com/
>>
>> Only 6/6 patch has been adjusted; all other patches remain unchanged.
> I don't want to rebase the branch just for that tiny change.
>
> If you want to fix it, send an incremental patch on top of v18.
The below patch:
https://lore.kernel.org/all/20240502182040.774759-1-sourabhjain@linux.ibm.com/
fixes the following build warning:
https://lore.kernel.org/oe-kbuild-all/202404261048.skfV5DDB-lkp@intel.com/
The fix patch is rebased on the linux-next/master branch.
Thanks,
Sourabh Jain
prev parent reply other threads:[~2024-05-02 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 2:27 [linux-next:master 7646/8170] arch/powerpc/kexec/crash.c:488:2-8: WARNING: NULL check before some freeing functions is not needed kernel test robot
2024-04-26 4:39 ` Sourabh Jain
2024-04-26 6:29 ` Sourabh Jain
2024-05-02 13:23 ` Michael Ellerman
2024-05-02 18:31 ` Sourabh Jain [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=dbc992da-ffa3-4d62-9e0c-734e9d180fec@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mpe@ellerman.id.au \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).