From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexandre TORGUE <alexandre.torgue@st•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the stm32 tree
Date: Wed, 4 May 2022 17:41:51 +1000 [thread overview]
Message-ID: <20220504174151.3bfeeaf8@canb.auug.org.au> (raw)
In-Reply-To: <AS8PR10MB4712B3354DACBB8A4F8309C9EEC39@AS8PR10MB4712.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
Hi Alexandre,
On Wed, 4 May 2022 07:28:53 +0000 Alexandre TORGUE <alexandre.torgue@st•com> wrote:
>
> Actually this patch has been already merged in Rob tree. I just
> cherry-pick it in my tree to avoid a merge conflict later for other
> maintainers. So I didn't add my "Signed-off-by".
You should add a SOB for every patch you add to your published tree.
That includes cherry-picked commits from other trees.
By the way, most maintainers (and Linus and I) are pretty adept at
sorting out merge conflicts (unless they are really complex, or course,
in which case you should probably have created a branch in one fo the
trees containing the conflicting commits from that tree and then merge
that branch into the both trees - and, of course, noted what is
happening in the merge commits).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-04 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 21:27 linux-next: Signed-off-by missing for commit in the stm32 tree Stephen Rothwell
2022-05-04 7:28 ` Alexandre TORGUE
2022-05-04 7:41 ` Stephen Rothwell [this message]
2022-05-04 8:27 ` Alexandre TORGUE
-- strict thread matches above, loose matches on Subject: below --
2022-06-20 21:51 Stephen Rothwell
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=20220504174151.3bfeeaf8@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alexandre.torgue@st$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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