From: Sedat Dilek <sedat.dilek@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
llvm@lists.linux.dev, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Linux 5.15-rc3
Date: Fri, 1 Oct 2021 17:44:13 +0200 [thread overview]
Message-ID: <CA+icZUUEmCR25dPfK16JB2V5wJfkuDLj3Dm+_BOAsfn_vUPRBw@mail.gmail.com> (raw)
In-Reply-To: <20210927214715.GE964074@nvidia.com>
On Mon, Sep 27, 2021 at 11:47 PM Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> On Mon, Sep 27, 2021 at 10:48:42PM +0200, Sedat Dilek wrote:
> > [ Please CC me I am not subscribed to LKML and linux-rdma ]
> >
> > Hi,
> >
> > with CONFIG_INFINIBAND_QIB=m I observe a build-error since Linux
> > v5.13-rc1 release.
> > This is with LLVM/Clang >= v13.0.0-rc3 on my Debian/unstable AMD64 system.
> >
> > For details see ClangBuiltLinux issue #1452 (see [1]).
> >
> > The fix is pending in rdma.git#for-rc (see [2]):
> >
> > commit 3110b942d36b961858664486d72f815d78c956c3
> > "IB/qib: Fix clang confusion of NULL pointer comparison"
> >
> > Dunno if there was a pull-request from linux-rdma folks.
> > Cannot say if it is worth taking this directly...?
>
> It should come as a PR this week, I don't think we need to do anything
> special urgent here, do we?
>
For the followers of this issue:
Commit is now in Linus Git.
- Sedat -
[1] https://git.kernel.org/linus/3110b942d36b961858664486d72f815d78c956c3
next prev parent reply other threads:[~2021-10-01 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 20:48 Linux 5.15-rc3 Sedat Dilek
2021-09-27 21:47 ` Jason Gunthorpe
2021-09-27 21:48 ` Nick Desaulniers
2021-09-27 21:49 ` Sedat Dilek
2021-10-01 15:44 ` Sedat Dilek [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-26 21:21 Linus Torvalds
2021-09-27 11:05 ` Guenter Roeck
2021-09-27 18:55 ` Linus Torvalds
2021-09-27 20:09 ` Thomas Bogendoerfer
2021-09-27 20:46 ` Linus Torvalds
2021-09-30 13:42 ` Guenter Roeck
2021-09-27 22:31 ` Michael S. Tsirkin
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=CA+icZUUEmCR25dPfK16JB2V5wJfkuDLj3Dm+_BOAsfn_vUPRBw@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).