linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Michael Walle <michael@walle.cc>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Subject: Re: [PATCH] gpio: regmap: move drvdata to config data
Date: Sat, 5 Jun 2021 00:13:20 +0200	[thread overview]
Message-ID: <CACRpkdYsh7=9KCHW8G8_qKoGy-f40rdTLUiE2dkzFGHc6KzLYQ@mail.gmail.com> (raw)
In-Reply-To: <62d131e0c2f16d647c36406ae8f9efba@walle.cc>

On Sat, Jun 5, 2021 at 12:03 AM Michael Walle <michael@walle.cc> wrote:
> Am 2021-06-05 00:00, schrieb Linus Walleij:
>
> >> Btw, I'm not sure how to handle this "was part of another patch by
> >> another
> >> author" thing. Should I leave the Sob and just add mine?
> >
> > Ideally just stack Sign-offs it is called the "delivery path".
>
> Even if it is just a subset of the original patch?

Yeah it's just an indication of whose hands typed thes characters.
Something with copyright law actually, nothing to do with actual
attribution. See (11) here:
https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html

Author: should reflect the person who wrote the majority of the
code however.

Yours,
Linus Walleij

      reply	other threads:[~2021-06-04 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 11:04 [PATCH] gpio: regmap: move drvdata to config data Michael Walle
2021-06-04 22:00 ` Linus Walleij
2021-06-04 22:03   ` Michael Walle
2021-06-04 22:13     ` Linus Walleij [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='CACRpkdYsh7=9KCHW8G8_qKoGy-f40rdTLUiE2dkzFGHc6KzLYQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=michael@walle.cc \
    /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).