From: "Jiang, Dave" <dave.jiang@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the nvdimm tree
Date: Sat, 21 Jul 2018 15:00:24 +0000 [thread overview]
Message-ID: <E0B67B6C-0862-4E2F-9796-C266E6ECF4FE@intel.com> (raw)
In-Reply-To: <20180722003608.42e7164c@canb.auug.org.au>
> On Jul 21, 2018, at 7:36 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi Dan,
>
> Commits
>
> 212a28b4dae9 ("MAINTAINERS: Add Jan Kara for filesystem DAX")
> 30153e5ba54d ("MAINTAINERS: update Ross Zwisler's email address")
>
> are missing a Signed-off-by from their committer.
That’s my fault. I’ll fix.
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2018-07-21 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 14:36 linux-next: Signed-off-by missing for commits in the nvdimm tree Stephen Rothwell
2018-07-21 15:00 ` Jiang, Dave [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=E0B67B6C-0862-4E2F-9796-C266E6ECF4FE@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).