linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov89@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	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 drm-misc tree
Date: Mon, 13 Nov 2023 21:56:32 -0500	[thread overview]
Message-ID: <530b6100-4f4e-4b3d-8fea-5b316e989633@gmail.com> (raw)
In-Reply-To: <20231114134506.2ba0de1f@canb.auug.org.au>


[-- Attachment #1.1.1: Type: text/plain, Size: 1780 bytes --]

On 2023-11-13 21:45, Stephen Rothwell wrote:
> Hi Luben,
> 
> On Mon, 13 Nov 2023 20:32:40 -0500 Luben Tuikov <ltuikov89@gmail.com> wrote:
>>
>> On 2023-11-13 20:08, Luben Tuikov wrote:
>>> On 2023-11-13 15:55, Stephen Rothwell wrote:  
>>>> Hi all,
>>>>
>>>> Commit
>>>>
>>>>   0da611a87021 ("dma-buf: add dma_fence_timestamp helper")
>>>>
>>>> is missing a Signed-off-by from its committer.
>>>>  
>>>
>>> In order to merge the scheduler changes necessary for the Xe driver, those changes
>>> were based on drm-tip, which included this change from drm-misc-fixes, but which
>>> wasn't present in drm-misc-next.
>>>
>>> I didn't want to create a merge conflict between drm-misc-next and drm-misc-fixes,
>>> when pulling that change from drm-misc-next to drm-misc-fixes, so that I can apply  
>>
>> ... when pulling that change from from drm-misc-fixes into drm-misc-next, so that I can apply...
>>
>>> the Xe scheduler changes on top of drm-misc-next.  
>>
>> The change in drm-misc-fixes is b83ce9cb4a465b. The latter is contained
>> in linus-master, and in drm-misc-fixes, while the former is in drm-misc-next.
>> When we merge linus-master/drm-misc-fixes into drm-misc-next, or whichever way
>> it happens, I'd like to avoid a merge conflict, but wanted to expedite the changes
>> for Xe.
> 
> None of that is relevant ... if you commit a patch to a tree that will
> be in the linux kernel tree, you must add your Signed-off-by to the commit.

Hi Stephen,

Noted!

So I always do this when I do git-am and such, but wasn't sure for this one single cherry-pick whose
original author was the committer in drm-misc-fixes, but will add my Signed-off-by in those
rare circumstances.

Thanks for the clarification!
-- 
Regards,
Luben

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 677 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2023-11-14  2:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 20:55 linux-next: Signed-off-by missing for commit in the drm-misc tree Stephen Rothwell
2023-11-14  1:08 ` Luben Tuikov
2023-11-14  1:32   ` Luben Tuikov
2023-11-14  2:45     ` Stephen Rothwell
2023-11-14  2:56       ` Luben Tuikov [this message]
2023-11-14  3:08         ` Stephen Rothwell
2023-11-14 23:46           ` Luben Tuikov
2023-11-16  8:11             ` Maxime Ripard
2023-11-16  8:27               ` Daniel Vetter
2023-11-22 12:00                 ` Maxime Ripard
2023-11-22 22:49                   ` Luben Tuikov
2023-11-24 13:20                     ` Jani Nikula
2023-11-24 22:08                       ` Luben Tuikov
2023-11-16  9:22         ` Maxime Ripard
2023-11-17  3:25           ` Luben Tuikov

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=530b6100-4f4e-4b3d-8fea-5b316e989633@gmail.com \
    --to=ltuikov89@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).