From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: RDMA mailing list <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Prepared RDMA Tree for 4.7
Date: Thu, 12 May 2016 22:01:17 -0400 [thread overview]
Message-ID: <9dbc023f-e442-843a-ab68-eec38ca1d6b7@redhat.com> (raw)
In-Reply-To: <20160512174406.GB11827-2ukJVAZIZ/Y@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]
On 05/12/2016 01:44 PM, Leon Romanovsky wrote:
> Hi Doug,
>
> I prepared the base tree [1] with patches sent to RDMA mailing and passed review.
You can't know that. The reason I say that is because they have to pass
my review as well, and that's usually an implicit thing. If I review
them and they have already passed list review and they pass my review,
then I include them. If they don't pass my review (which isn't often if
the other people on the list have already spoke up, but does happen),
then I ask for revisions. If you take them without an explicit review
from me, then you don't know if I'll ask for a revision or not. It's
premature.
> This base tree is part of linux-next and kbuild system, and it passed
> sanity checks.
Most, there was a linux-next build failure that I'm sure is related to a
change I hadn't had a chance to look into yet but looked fishy to me
(the move to put ib_addr into ib_core looks like it's broken, but I
hadn't delved into the code to verify it...the linux-next build failure
from tonight makes me thing that it is).
> I believe that it will save you a lot of work and time if you use it
> as a base for next merge window submission (4.7).
Not really. I still have to review the patches, and I still have to
update patchworks, and when I'm sorting through patchworks is when I get
the patches to include. The incremental time to grab the patches out of
patchworks and run git am -s on the bundle is negligible. The real time
is in reading the patches, and this doesn't save me any of that time.
The help is appreciated though ;-)
> The topics which were added:
> * topic/fix-core
> * topic/hfi1
> * topic/i40iw
> * topic/ipoib
> * topic/iw_cxgb4
> * topic/iwcm
> * topic/nes
> * topic/rdma-rw-api
> * topic/srp
>
> [1]
> Git repository:
> git://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git rdma-next
>
> Gitweb:
> https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/log/?h=rdma-next
>
> Thanks.
>
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2016-05-13 2:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 17:44 Prepared RDMA Tree for 4.7 Leon Romanovsky
[not found] ` <20160512174406.GB11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-12 17:47 ` Leon Romanovsky
2016-05-13 2:01 ` Doug Ledford [this message]
[not found] ` <9dbc023f-e442-843a-ab68-eec38ca1d6b7-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-13 4:22 ` Leon Romanovsky
[not found] ` <20160513042217.GD11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-13 16:31 ` Doug Ledford
[not found] ` <9e5233c8-6641-7f6b-3825-1b67eb70c05b-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-14 4:33 ` Leon Romanovsky
[not found] ` <20160514043353.GG11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-14 13:09 ` Doug Ledford
[not found] ` <f9210e1d-667d-5f62-f1bd-7545a0ff6153-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-15 6:00 ` Leon Romanovsky
[not found] ` <20160515060005.GH11827-2ukJVAZIZ/Y@public.gmane.org>
2016-05-16 20:15 ` Doug Ledford
[not found] ` <04c7b983-66b4-0609-9cf4-3c7b1e126a53-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-05-17 13:38 ` Leon Romanovsky
2016-05-18 13:18 ` Daniel Jurgens
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=9dbc023f-e442-843a-ab68-eec38ca1d6b7@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox