From: "Schumaker, Anna" <Anna.Schumaker@netapp.com>
To: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"trondmy@gmail.com" <trondmy@gmail.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the nfs tree
Date: Tue, 9 Jul 2019 14:30:50 +0000 [thread overview]
Message-ID: <ed6656ad172920882862e5571b6c237a31974bc3.camel@netapp.com> (raw)
In-Reply-To: <CAABAsM7jKzWPNoe63LU33tVfn7a88ZP9yzp4Bb1BN2TDWMxgjQ@mail.gmail.com>
On Sun, 2019-07-07 at 17:30 -0400, Trond Myklebust wrote:
> NetApp Security WARNING: This is an external email. Do not click
> links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
>
> On Sun, 7 Jul 2019 at 17:29, Stephen Rothwell <sfr@canb.auug.org.au>
> wrote:
> > Hi all,
> >
> > Commits
> >
> > fe9ad197bd8a ("xprtrdma: Remove the RPCRDMA_REQ_F_PENDING flag")
> > 08d720bcd822 ("xprtrdma: Fix occasional transport deadlock")
> > beb843739ea0 ("xprtrdma: Replace use of xdr_stream_pos in
> > rpcrdma_marshal_req")
> >
> > are missing a Signed-off-by from their committer.
> >
>
> Anna?
Looks like I missed the "-s" flag to `git-am` when I was applying
these. I just fixed it locally, do you want me to send you a new pull
request?
Anna
next prev parent reply other threads:[~2019-07-09 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 21:28 linux-next: Signed-off-by missing for commits in the nfs tree Stephen Rothwell
2019-07-07 21:30 ` Trond Myklebust
2019-07-09 14:30 ` Schumaker, Anna [this message]
2019-07-09 14:55 ` Trond Myklebust
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=ed6656ad172920882862e5571b6c237a31974bc3.camel@netapp.com \
--to=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trondmy@gmail.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