From: Jason Gunthorpe <jgg@ziepe.ca>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Doug Ledford <dledford@redhat.com>,
Bernard Metzler <bmt@zurich.ibm.com>,
"Torvalds, Linus" <torvalds@linux-foundation.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST] Please pull rdma.git
Date: Mon, 19 Aug 2019 09:14:00 -0300 [thread overview]
Message-ID: <20190819121400.GA5058@ziepe.ca> (raw)
In-Reply-To: <CAMuHMdWp+g-W0rJtVTWEiJpbhcV7GoSkub11fZPMUbhJcxMUNA@mail.gmail.com>
On Mon, Aug 19, 2019 at 12:08:16PM +0200, Geert Uytterhoeven wrote:
> Hi Doug, Bernard,
>
> On Wed, Aug 14, 2019 at 5:00 PM Doug Ledford <dledford@redhat.com> wrote:
> > Fairly small pull request for -rc3. I'm out of town the rest of this
> > week, so I made sure to clean out as much as possible from patchworks in
> > enough time for 0-day to chew through it (Yay! for 0-day being back
> > online! :-)). Jason might send through any emergency stuff that could
> > pop up, otherwise I'm back next week.
> >
> > The only real thing of note is the siw ABI change. Since we just merged
> > siw *this* release, there are no prior kernel releases to maintain
> > kernel ABI with. I told Bernard that if there is anything else about
> > the siw ABI he thinks he might want to change before it goes set in
> > stone, he should get it in ASAP. The siw module was around for several
> > years outside the kernel tree, and it had to be revamped considerably
> > for inclusion upstream, so we are making no attempts to be backward
> > compatible with the out of tree version. Once 5.3 is actually released,
> > we will have our baseline ABI to maintain.
>
> [...]
>
> > - Allow siw to be built on 32bit arches (siw, ABI change, but OK since
> > siw was just merged this merge window and there is no prior released
> > kernel to maintain compatibility with and we also updated the
> > rdma-core user space package to match)
>
> > Bernard Metzler (1):
> > RDMA/siw: Change CQ flags from 64->32 bits
>
> Obviously none of this was ever compiled for a 32-bit platform?!?
It is puzzling that 0-day or anyone testing linux-next hasn't noticed
this in that last 7 weeks are so..
Jason
next prev parent reply other threads:[~2019-08-19 12:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 14:59 [PULL REQUEST] Please pull rdma.git Doug Ledford
2019-08-14 18:25 ` pr-tracker-bot
2019-08-19 10:08 ` Geert Uytterhoeven
2019-08-19 12:14 ` Jason Gunthorpe [this message]
2019-08-19 12:29 ` Geert Uytterhoeven
2019-08-19 12:48 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2019-08-30 15:42 Doug Ledford
2019-08-30 16:40 ` pr-tracker-bot
[not found] <5b0aa103f6007e1887f9b2cacaec8015834589b8.camel@xsintricity.com>
2019-08-23 19:14 ` Doug Ledford
2019-08-02 14:39 Doug Ledford
2019-08-02 22:10 ` pr-tracker-bot
2019-06-21 19:42 Doug Ledford
2019-06-21 22:35 ` pr-tracker-bot
2018-12-13 16:56 Doug Ledford
2018-12-13 21:15 ` pr-tracker-bot
[not found] <58466423-c87e-3921-101e-bffab8989fd8@redhat.com>
[not found] ` <20161117184950.GP4240@leon.nu>
[not found] ` <582E089A.3040106@redhat.com>
[not found] ` <20161117200203.GQ4240@leon.nu>
2016-11-17 22:24 ` Or Gerlitz
2016-11-18 2:01 ` Doug Ledford
2016-11-19 19:46 ` Or Gerlitz
2016-11-19 23:11 ` Doug Ledford
2016-11-20 12:53 ` Leon Romanovsky
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=20190819121400.GA5058@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=bmt@zurich.ibm.com \
--cc=dledford@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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).