From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>, Or Gerlitz <ogerlitz@mellanox.com>
Cc: Christoph Hellwig <hch@lst.de>,
"J. Bruce Fields" <bfields@fieldses.org>,
Doug Ledford <dledford@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
LKML Kernel <linux-kernel@vger.kernel.org>,
Ira Weiny <ira.weiny@intel.com>
Subject: Re: linux-next: manual merge of the rdma tree with the nfsd tree
Date: Wed, 6 Jan 2016 11:48:49 -0500 [thread overview]
Message-ID: <568D4571.7030201@Netapp.com> (raw)
In-Reply-To: <2118F38A-846F-4690-A6E8-0BA7A437D567@oracle.com>
On 01/06/2016 11:33 AM, Chuck Lever wrote:
>
>> On Jan 6, 2016, at 10:52 AM, Or Gerlitz <ogerlitz@mellanox.com> wrote:
>>
>> On 1/6/2016 5:20 PM, Chuck Lever wrote:
>>>> Chuck,
>>>>>
>>>>> Lets be concrete... anything wrong with patch [1]?
>>> Yes. It is missing Acked-by: lines from the maintainers of
>>> those files.
>>>
>>> All changes to files under net/sunrpc need an Ack from one
>>> of the maintainers listed in MAINTAINERS for that directory,
>>> if the changes are going through another maintainer's tree.
>>>
>>> I have been personally asked to remind folks that the
>>> nfs-sunrpc maintainers do not read linux-rdma, so they
>>> must be contacted directly (and cc: linux-nfs) as part of
>>> proposing finished patches in that area.
>>
>> I did that!!
>>
>> I copied you and Anna on the patch [1].
>
> The marc.info archive does not preserve To: or Cc:
> fields on e-mail. I had to look in my own inbox to
> confirm who the recipients were.
>
> Anna was the only NFS maintainer listed, and
> linux-nfs was not included on that e-mail at all.
> Did Anna ever reply with an Acked-by ? I don't see
> that in either the archive or my own inbox.
I'm not sure if I ever replied to that one. This patch was part of an alternative to Christoph's deviceattr cleanup, right? The NFS client bits looked okay to me, but I held off on replying to see which version was accepted. Feel free to add my:
Acked-by: Anna Schumaker <Anna.Schumaker@netapp.com>
Anna
>
> Bruce needs to Ack the svc_rdma_transport.c hunks.
>
>
>> Again, lets be concrete, this very small cleanup was picked and merged, anything there
>> need to be fixed?
>
> I have rebased on Doug's current for-4.5, and will
> be testing today before submitting my for-4.5 patches
> again. Your changes are mechanical, so I don't expect
> to encounter a technical problem.
>
> However, I would be more comfortable if the missing
> Acks were fixed in Doug's tree (with Anna and Bruce's
> permission, of course) before Linus pulls.
>
>
>> Or.
>>
>> [1] http://marc.info/?l=linux-rdma&m=145042924110411&w=2
>>
>>
>>> Unfortunately I have not been able to review every patch
>>> that has come by on linux-rdma in the past 9 months to
>>> ensure the eyes are dotted and tees crossed. More than
>>> a few commits in the tree are missing the proper tags.
>>>
>>>
>>>> [1] commit e3e45b1 "xprtrdma: Avoid calling ib_query_device"
>>>>
>>>> in git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git k.o/for-4.5
>>>>
>>>> http://git.kernel.org/cgit/linux/kernel/git/dledford/rdma.git/commit/?h=k.o/for-4.5&id=e3e45b1b43988b99007a9908ca0ba738b3fbd0ff
>>>>
>>
>
> --
> Chuck Lever
>
>
>
>
next prev parent reply other threads:[~2016-01-06 16:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 2:30 linux-next: manual merge of the rdma tree with the nfsd tree Stephen Rothwell
2016-01-04 1:44 ` Stephen Rothwell
2016-01-04 2:53 ` Doug Ledford
2016-01-04 19:36 ` J. Bruce Fields
2016-01-06 12:01 ` Chuck Lever
2016-01-06 12:14 ` Or Gerlitz
2016-01-06 12:15 ` Christoph Hellwig
2016-01-06 12:22 ` Or Gerlitz
2016-01-06 12:28 ` Christoph Hellwig
2016-01-06 17:54 ` Doug Ledford
2016-01-06 14:24 ` Chuck Lever
2016-01-06 14:46 ` Or Gerlitz
2016-01-06 15:20 ` Chuck Lever
2016-01-06 15:52 ` Or Gerlitz
2016-01-06 16:33 ` Chuck Lever
2016-01-06 16:38 ` Or Gerlitz
2016-01-06 16:48 ` Anna Schumaker [this message]
2016-01-06 12:27 ` Chuck Lever
2016-01-06 16:25 ` J. Bruce Fields
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=568D4571.7030201@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sfr@canb.auug.org.au \
/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).