From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: RDMA mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Bart Van Assche
<bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>,
Dennis Dalessandro
<dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
Shiraz Saleem
<shiraz.saleem-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Missing Patches in Linux Kernel RDMA
Date: Tue, 10 Jan 2017 16:30:18 +0200 [thread overview]
Message-ID: <20170110143018.GM7218@mtr-leonro.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
Hi Doug,
While reviewing patches on mailing list, I was amazed to see
patches accepted before, marked such in patchworks but don't
exist in the Linus's tree.
The first patch which brought my attention was Christoph's change
"IB: merge struct ib_device_attr into struct ib_device" [1]. The other
missed patches were from our pre-ABI series "Refactor RDMA IOCTL
declarations" [2, 3].
I'm adding to CC major contributors to this subsystem, since I don't know
if any other patches are missing too and don't know how to check it without
doing full compare of Linus's tree with linux-rdma patchworks.
However for these 7 patches, can you please grab them from patchworks again
and resubmit?
Thanks
[1] https://patchwork.kernel.org/patch/7372541/
[2] https://www.spinics.net/lists/linux-rdma/msg39954.html
[3] https://patchwork.kernel.org/patch/9312603/
https://patchwork.kernel.org/patch/9312593/
https://patchwork.kernel.org/patch/9312597/
https://patchwork.kernel.org/patch/9312601/
https://patchwork.kernel.org/patch/9312595/
https://patchwork.kernel.org/patch/9312599/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-01-10 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:30 Leon Romanovsky [this message]
[not found] ` <20170110143018.GM7218-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-10 14:36 ` Missing Patches in Linux Kernel RDMA Christoph Hellwig
[not found] ` <20170110143658.GA26753-jcswGhMUV9g@public.gmane.org>
2017-01-10 16:51 ` Doug Ledford
[not found] ` <1484067095.2149.12.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-10 18:50 ` Leon Romanovsky
[not found] ` <20170110185040.GO7218-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-10 18:54 ` Doug Ledford
2017-01-10 16:53 ` Doug Ledford
[not found] ` <1484067238.2149.15.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-10 18:28 ` Leon Romanovsky
[not found] ` <20170110182815.GN7218-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-01-10 18:52 ` Doug Ledford
[not found] ` <1484074377.2149.23.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-10 19:06 ` 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=20170110143018.GM7218@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org \
--cc=dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shiraz.saleem-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.