From: Alexandre TORGUE <alexandre.torgue@st•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
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 08:27:17 +0000 [thread overview]
Message-ID: <AS8PR10MB47121BA9429673F0729D6DF3EEC39@AS8PR10MB4712.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220504174151.3bfeeaf8@canb.auug.org.au>
Stephen
ST Restricted
> -----Original Message-----
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Sent: Wednesday, May 4, 2022 9:42 AM
> 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
>
> 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.
>
Ok I add it now and update the stm32-next branch.
> 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).
> --
I have no doubt that you could have fixed it 😊. It was also easier for me to add my changes on top of it.
Cheers
Alex
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2022-05-04 8:27 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
2022-05-04 8:27 ` Alexandre TORGUE [this message]
-- 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=AS8PR10MB47121BA9429673F0729D6DF3EEC39@AS8PR10MB4712.EURPRD10.PROD.OUTLOOK.COM \
--to=alexandre.torgue@st$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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