From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
DRI <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-gfx] linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree
Date: Thu, 29 Oct 2020 10:08:05 +0200 [thread overview]
Message-ID: <87ft5xihei.fsf@intel.com> (raw)
In-Reply-To: <160392160276.31966.3847690661999837078@build.alporthouse.com>
On Wed, 28 Oct 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Stephen Rothwell (2020-10-28 21:28:23)
>> Hi all,
>>
>> Commit
>>
>> d13208a88f41 ("lockdep: Fix nr_unused_locks")
>>
>> is missing a Signed-off-by from its author.
>>
>> Also, the author's email name is missing the leading 'P'.
>
> And it shouldn't be in the drm-intel-fixes tree.
It's temporarily on top of the fixes branch to allow our CI to test the
branch. We weren't getting results on anything -rc1 based because of
this.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
DRI <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree
Date: Thu, 29 Oct 2020 10:08:05 +0200 [thread overview]
Message-ID: <87ft5xihei.fsf@intel.com> (raw)
In-Reply-To: <160392160276.31966.3847690661999837078@build.alporthouse.com>
On Wed, 28 Oct 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Stephen Rothwell (2020-10-28 21:28:23)
>> Hi all,
>>
>> Commit
>>
>> d13208a88f41 ("lockdep: Fix nr_unused_locks")
>>
>> is missing a Signed-off-by from its author.
>>
>> Also, the author's email name is missing the leading 'P'.
>
> And it shouldn't be in the drm-intel-fixes tree.
It's temporarily on top of the fixes branch to allow our CI to test the
branch. We weren't getting results on anything -rc1 based because of
this.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
DRI <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree
Date: Thu, 29 Oct 2020 10:08:05 +0200 [thread overview]
Message-ID: <87ft5xihei.fsf@intel.com> (raw)
In-Reply-To: <160392160276.31966.3847690661999837078@build.alporthouse.com>
On Wed, 28 Oct 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Stephen Rothwell (2020-10-28 21:28:23)
>> Hi all,
>>
>> Commit
>>
>> d13208a88f41 ("lockdep: Fix nr_unused_locks")
>>
>> is missing a Signed-off-by from its author.
>>
>> Also, the author's email name is missing the leading 'P'.
>
> And it shouldn't be in the drm-intel-fixes tree.
It's temporarily on top of the fixes branch to allow our CI to test the
branch. We weren't getting results on anything -rc1 based because of
this.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-29 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 21:28 [Intel-gfx] linux-next: Signed-off-by missing for commit in the drm-intel-fixes tree Stephen Rothwell
2020-10-28 21:28 ` Stephen Rothwell
2020-10-28 21:28 ` Stephen Rothwell
2020-10-28 21:46 ` [Intel-gfx] " Chris Wilson
2020-10-28 21:46 ` Chris Wilson
2020-10-28 21:46 ` Chris Wilson
2020-10-29 8:08 ` Jani Nikula [this message]
2020-10-29 8:08 ` Jani Nikula
2020-10-29 8:08 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2021-02-02 20:02 [Intel-gfx] " Stephen Rothwell
2021-02-03 9:59 ` Jani Nikula
2017-12-07 22:15 Stephen Rothwell
2017-12-11 10:31 ` [Intel-gfx] " Joonas Lahtinen
2017-12-11 20:10 ` Daniel Vetter
2017-12-11 20:10 ` Daniel Vetter
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=87ft5xihei.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rodrigo.vivi@intel.com \
--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 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.