From: jerome Neanne <jneanne@baylibre.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Jon Cormier <jcormier@criticallink.com>
Cc: linus.walleij@linaro.org, brgl@bgdev.pl, tony@atomide.com,
lee@kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] gpio: tps65219: add GPIO support for TPS65219 PMIC
Date: Tue, 28 Feb 2023 12:18:41 +0100 [thread overview]
Message-ID: <741eb8c3-ad05-19e2-2604-9cd9c97c4ef4@baylibre.com> (raw)
In-Reply-To: <CAHp75Vc52cqPaTFTvi2E-3Gg6gAsDWc7wSWjn7wMuhcxWqFXBA@mail.gmail.com>
On 27/02/2023 20:51, Andy Shevchenko wrote:
>>>> Signed-off-by: Jonathan Cormier<jcormier@criticallink.com>
>>>> Signed-off-by: Jerome Neanne<jneanne@baylibre.com>
>>> Not sure how to interpet this along with the From line.
>> Are two sign-offs not allowed/expected? I wrote the initial
>> implementation of this driver and Jerome updated it and is handling
>> submitting it since he did the rest of the TPS65219 drivers.
> 1. Submitter's SoB must be the last SoB in the chain.
> 2. Developers also need to be marked with Co-developed-by.
Got it! My mistake. I'll fix following your instructions.
next prev parent reply other threads:[~2023-02-28 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 11:38 [PATCH 0/2] Add support for TI TPS65219 PMIC GPIO interface Jerome Neanne
2023-02-24 11:38 ` [PATCH 1/2] gpio: tps65219: add GPIO support for TPS65219 PMIC Jerome Neanne
2023-02-24 12:16 ` andy.shevchenko
2023-02-24 12:18 ` andy.shevchenko
2023-02-27 19:20 ` Jon Cormier
2023-02-27 19:51 ` Andy Shevchenko
2023-02-28 11:18 ` jerome Neanne [this message]
2023-02-24 11:38 ` [PATCH 2/2] mfd: tps65219: Add gpio cell instance Jerome Neanne
2023-02-24 12:17 ` andy.shevchenko
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=741eb8c3-ad05-19e2-2604-9cd9c97c4ef4@baylibre.com \
--to=jneanne@baylibre.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=jcormier@criticallink.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 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.