From: Ley Foon Tan <ley.foon.tan@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Ley Foon Tan <lftan@altera.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 nios2 tree
Date: Mon, 12 Feb 2018 10:16:07 +0800 [thread overview]
Message-ID: <1518401767.49408.6.camel@intel.com> (raw)
In-Reply-To: <20180212131414.0ca70c63@canb.auug.org.au>
On Mon, 2018-02-12 at 13:14 +1100, Stephen Rothwell wrote:
> Hi Ley,
>
> On Mon, 12 Feb 2018 09:23:49 +0800 Ley Foon Tan <ley.foon.tan@intel.c
> om> wrote:
> >
> >
> > On Mon, 2018-02-12 at 09:20 +1100, Stephen Rothwell wrote:
> > >
> > >
> > > Commits
> > >
> > > 5d13c7317998 ("nios2: dts: Remove leading 0x and 0s from
> > > bindings
> > > notation")
> > > e0691ebb33c1 ("nios2: defconfig: Cleanup from old Kconfig
> > > options")
> > >
> > > are missing a Signed-off-by from their committer.
> > There are Signed-off-by in the commits.
> >
> > Signed-off-by: Mathieu Malaterre <malat@debian.org>
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> They are the authors of the patches, but you are the committer i.e.
> you
> are on the path form the authors to Linus, so you need to add a
> Signed-off-by tag as well. I see Linus has merged theses commits
> now,
> so there is nothing to be done for them, but in the future please add
> a
> Signed-off-by tag for anything that you commit.
>
> See section 11 of Documentation/process/submitting-patches.rst
> --
Noted. Thanks.
Regards
Ley Foon
prev parent reply other threads:[~2018-02-12 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 22:20 linux-next: Signed-off-by missing for commits in the nios2 tree Stephen Rothwell
2018-02-12 1:23 ` Ley Foon Tan
2018-02-12 2:14 ` Stephen Rothwell
2018-02-12 2:16 ` Ley Foon Tan [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=1518401767.49408.6.camel@intel.com \
--to=ley.foon.tan@intel.com \
--cc=lftan@altera.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).