From: "Schumaker, Anna" <Anna.Schumaker@netapp.com>
To: "davem@davemloft.net" <davem@davemloft.net>,
"gustavo@embeddedor.com" <gustavo@embeddedor.com>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"trond.myklebust@hammerspace.com"
<trond.myklebust@hammerspace.com>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] xprtrdma: Use struct_size() in kzalloc()
Date: Tue, 28 May 2019 13:56:15 +0000 [thread overview]
Message-ID: <5e8c92372afae86af71564a357691b3e4283640a.camel@netapp.com> (raw)
In-Reply-To: <c8d7982b-cf18-adc0-aa70-81b8ee5ae780@embeddedor.com>
On Thu, 2019-05-23 at 18:43 -0500, Gustavo A. R. Silva wrote:
>
> On 5/23/19 6:32 PM, David Miller wrote:
> > From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
> > Date: Thu, 23 May 2019 17:36:00 -0500
> >
> > > Hi Dave,
> > >
> > > I wonder if you can take this patch.
> >
> > The sunrpc/nfs maintainer should take this. I never take patches in that
> > area.
> >
>
> Yep. Chuck just let me know that Anna is who take these patches.
>
> Hopefully, she will take this one soon.
I've applied this to push out later in the week. Thanks for pointing it out to
me!
Anna
>
> Thanks
> --
> Gustavo
prev parent reply other threads:[~2019-05-28 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 0:46 [PATCH net-next] xprtrdma: Use struct_size() in kzalloc() Gustavo A. R. Silva
2019-01-31 14:11 ` Chuck Lever
2019-02-08 3:49 ` Gustavo A. R. Silva
2019-03-28 20:41 ` Gustavo A. R. Silva
2019-05-23 22:36 ` Gustavo A. R. Silva
2019-05-23 23:02 ` Chuck Lever
2019-05-23 23:32 ` David Miller
2019-05-23 23:43 ` Gustavo A. R. Silva
2019-05-28 13:56 ` Schumaker, Anna [this message]
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=5e8c92372afae86af71564a357691b3e4283640a.camel@netapp.com \
--to=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=gustavo@embeddedor.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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).