From: Greg KH <greg@kroah.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, stable-commits@vger.kernel.org,
Mike Marciniszyn <infinipath@intel.com>,
Doug Ledford <dledford@redhat.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>
Subject: Re: Patch "IB/qib: Fix null pointer subtraction compiler warning" has been added to the 5.14-stable tree
Date: Fri, 24 Sep 2021 14:28:48 +0200 [thread overview]
Message-ID: <YU3EgPnHcCnBYLOx@kroah.com> (raw)
In-Reply-To: <20210924114933.GV964074@nvidia.com>
On Fri, Sep 24, 2021 at 08:49:33AM -0300, Jason Gunthorpe wrote:
> On Fri, Sep 24, 2021 at 07:44:20AM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > IB/qib: Fix null pointer subtraction compiler warning
> >
> > to the 5.14-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > ib-qib-fix-null-pointer-subtraction-compiler-warning.patch
> > and it can be found in the queue-5.14 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Please don't take this one, it causes compilation failures on some
> clang versions. I have another fix queued up that will sort it out
> for all compiler versions.
Ok, now dropped, thanks.
greg k-h
prev parent reply other threads:[~2021-09-24 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210924114420.106491-1-sashal@kernel.org>
2021-09-24 11:49 ` Patch "IB/qib: Fix null pointer subtraction compiler warning" has been added to the 5.14-stable tree Jason Gunthorpe
2021-09-24 12:28 ` Greg KH [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=YU3EgPnHcCnBYLOx@kroah.com \
--to=greg@kroah.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=infinipath@intel.com \
--cc=jgg@nvidia.com \
--cc=sashal@kernel.org \
--cc=sean.hefty@intel.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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