From: Manasi Navare <manasi.d.navare@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [Intel-gfx] linux-next: Signed-off-by missing for commit in the drm-intel tree
Date: Tue, 6 Nov 2018 16:07:25 -0800 [thread overview]
Message-ID: <20181107000724.GJ26420@intel.com> (raw)
In-Reply-To: <20181107000034.GD2367@intel.com>
On Tue, Nov 06, 2018 at 04:00:34PM -0800, Rodrigo Vivi wrote:
> On Wed, Nov 07, 2018 at 06:59:29AM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Commit
> >
> > 35b876db4a42 ("drm/i915/dsc: Add slice_row_per_frame in DSC PPS programming")
> >
> > is missing a Signed-off-by from its committer.
>
> It seems the tag "Suggested-by:" tricked out our maintainer tools.
Hmm yea that makes sense since it did have suggested-by: me (committer)
so it skipped adding my sign-off.
Thanks for catching this and fixing it in tools.
Manasi
>
> from dim:
>
> # check for committer sign-off
> if ! git show -s $sha1 | grep -qi "S.*-by:.*$committer" ; then
>
> -----
>
> I will send a patch to our tools to spell signed-off-by directly.
>
> Thanks for reporting this out.
> Rodrigo.
>
> >
> > --
> > Cheers,
> > Stephen Rothwell
>
>
>
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-07 0:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 19:59 linux-next: Signed-off-by missing for commit in the drm-intel tree Stephen Rothwell
2018-11-06 19:59 ` Stephen Rothwell
2018-11-07 0:00 ` Rodrigo Vivi
2018-11-07 0:00 ` [Intel-gfx] " Rodrigo Vivi
2018-11-07 0:07 ` Manasi Navare [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-15 4:18 Stephen Rothwell
2021-08-06 6:36 ` Joonas Lahtinen
2021-08-09 14:05 ` Daniel Vetter
2021-08-09 16:19 ` Matt Roper
2021-08-10 6:27 ` Daniel Vetter
2021-08-11 5:56 ` Joonas Lahtinen
2021-08-11 7:16 ` Jani Nikula
2021-08-11 9:48 ` Daniel Vetter
2021-08-11 11:02 ` Jani Nikula
2021-08-11 15:15 ` Matt Roper
2021-08-11 14:09 ` Rodrigo Vivi
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=20181107000724.GJ26420@intel.com \
--to=manasi.d.navare@intel.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=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.