All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Chris Ball <chris@printf.net>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	Sebastian Rasmussen <sebras@gmail.com>
Subject: Re: [PATCH v2] mmc-utils: Merge the lsmmc tool into mmc-utils
Date: Tue, 2 Feb 2016 22:39:21 +0100	[thread overview]
Message-ID: <CACRpkdadeOgJfPXvpLyVZctSqjY7EdW1=TQmetBsQN=GDr7J3Q@mail.gmail.com> (raw)
In-Reply-To: <d59ece1ff066b7fd7c8b538a560f726751fb1f9a.1454401105.git.baolin.wang@linaro.org>

On Tue, Feb 2, 2016 at 9:21 AM, Baolin Wang <baolin.wang@linaro.org> wrote:

> The lsmmc tools contains an extensive parser of the CID, CSD, SCR, EXT_CSD
> registers from userspace. The utility works as-is and uses sysfs to read
> the register values.
>
> The original code is created by Sebastian Rasmussen and still lives in
> private git. It need to be merged into mmc-utils repository, which is
> convenient for testing MMC device from userspace.
>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>

Nitpicky formalia:

The SoB-chain should represent the delivery path of the code, so I think
it should be:

Signed-off-by: Sebastian Rasmussen <sebras@gmail.com>
Signed-off-by: Chris Ball <chris@printf.net>
Signed-off-by: Baolin Wang <baolin.wang@linaro.org>

..and then when Ulf merges it it get his SoB too.

Then the Author: has no strong rule by usually should
represent who wrote the majority of the code, so unless you've changes
more than 50% of the code, consider
git commit --amend --author="Sebastian Rasmussen <sebras@gmail.com>"
for this commit.

I usually don't care a lot about the latter but since it's a big and initial
commit I think it matters. If it's too diverse authors and unclear
contributor distribution, a mailing list can be used as author, c.f.
commit a8c21a5451d831e67b7a6fb910f9ca8bc7b43554

Thanks for working on this!

Yours,
Linus Walleij

  reply	other threads:[~2016-02-02 21:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  8:21 [PATCH v2] mmc-utils: Merge the lsmmc tool into mmc-utils Baolin Wang
2016-02-02 21:39 ` Linus Walleij [this message]
2016-02-03  2:26   ` Baolin Wang
2016-02-02 22:04 ` Sebastian Rasmussen
2016-02-03  2:34   ` Baolin Wang
2016-02-05  8:23 Baolin Wang
2016-02-05  9:29 ` Linus Walleij
2016-02-05 15:17   ` Sebastian Rasmussen
2016-02-16 20:02 ` Chris Ball
2016-02-17  2:31   ` Baolin Wang

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='CACRpkdadeOgJfPXvpLyVZctSqjY7EdW1=TQmetBsQN=GDr7J3Q@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=baolin.wang@linaro.org \
    --cc=broonie@kernel.org \
    --cc=chris@printf.net \
    --cc=linux-mmc@vger.kernel.org \
    --cc=sebras@gmail.com \
    --cc=ulf.hansson@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.