From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
linux-mtd@lists.infradead.org,
David Woodhouse <David.Woodhouse@intel.com>
Subject: Re: [PATCH V2 3/6] mtd: bcm47xxnflash: fix message
Date: Mon, 04 Feb 2013 11:02:48 +0200 [thread overview]
Message-ID: <1359968568.13791.31.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CACna6ry0B9nPZDUEDgYZnqM7YsGeDkWG9r6eKihbK+=WLqUcLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
On Mon, 2013-02-04 at 09:42 +0100, Rafał Miłecki wrote:
> 2013/2/4 Artem Bityutskiy <dedekind1@gmail.com>:
> > On Mon, 2013-01-28 at 11:25 +0100, Rafał Miłecki wrote:
> >> From: Hauke Mehrtens <hauke@hauke-m.de>
> >>
> >> This is not a serial flash driver, but a nand flash driver
> >>
> >> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> >> ---
> >> V2: break line to match 80 chars
> >
> > When sending v2 for individual patches, please, remember 2 things:
> >
> > 1. Keep them part of the original thread (ensure correct In-Reply-To:).
>
> Whoops, I've to learn how to make that with git send-email.
--in-reply-to=<identifier>
Pick the identifier from the Message-ID tag of the e-mail you are
replying to. E.g., save the e-mail as hauke.mbox file and do:
$ grep -i '^Message-ID:' hauke.mbox
Message-Id: <1359045599-1305-2-git-send-email-hauke@hauke-m.de>
which means that for this one the 'git send-email' option will be:
--in-reply-to="<1359045599-1305-2-git-send-email-hauke@hauke-m.de>"
> > 2. Add your own signed-off-by.
>
> It was so trivial... I wasn't sure if it's worth signing-it-by... ;)
Signed-off-by is not about how big were your changes, it roughly
speaking means that you confirm that the source of this patch for you is
Hauke Mehrtens.
See Documentation/SubmittingPatches
The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery
path.
I googled a bit and found also this:
http://kerneltrap.org/files/Jeremy/DCO.txt
which gives additional clue about what can be behind SOB.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-02-04 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 10:25 [PATCH V2 3/6] mtd: bcm47xxnflash: fix message Rafał Miłecki
2013-01-28 10:25 ` [PATCH V2 4/6] mtd: bcm47xxnflash: register this as normal driver Rafał Miłecki
2013-01-28 19:57 ` Hauke Mehrtens
2013-02-04 8:35 ` [PATCH V2 3/6] mtd: bcm47xxnflash: fix message Artem Bityutskiy
2013-02-04 8:42 ` Rafał Miłecki
2013-02-04 9:02 ` Artem Bityutskiy [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=1359968568.13791.31.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=zajec5@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