From: Matt Roper <matthew.d.roper@intel.com> To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>, DRI <dri-devel@lists.freedesktop.org>, Intel Graphics <intel-gfx@lists.freedesktop.org>, Jani Nikula <jani.nikula@linux.intel.com>, Rodrigo Vivi <rodrigo.vivi@intel.com>, Stephen Rothwell <sfr@canb.auug.org.au>, 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-intel tree Date: Mon, 9 Aug 2021 09:19:39 -0700 [thread overview] Message-ID: <20210809161939.GS1556418@mdroper-desk1.amr.corp.intel.com> (raw) In-Reply-To: <YRE2RwQ6XlUqbgmn@phenom.ffwll.local> On Mon, Aug 09, 2021 at 04:05:59PM +0200, Daniel Vetter wrote: > On Fri, Aug 06, 2021 at 09:36:56AM +0300, Joonas Lahtinen wrote: > > Hi Matt, > > > > Always use the dim tooling when applying patches, it will do the right > > thing with regards to adding the S-o-b. > > fd.o server rejects any pushes that haven't been done by dim, so how did > this get through? I definitely used dim for all of these patches, but I'm not sure how I lost my s-o-b on this one. Maybe when I edited the commit message after 'dim extract-tags' I accidentally deleted an extra line when I removed the extract-tags marker? It's the only patch where the line is missing, so it's almost certainly human error on my part rather than something dim did wrong. > Matt, can you pls figure out and type up the patch to > plug that hole? Are you referring to a patch for dim here? The i915 patch has already landed, so we can't change its commit message now. Matt > > Thanks, Daniel > > > > > Regards, Joonas > > > > Quoting Stephen Rothwell (2021-07-15 07:18:54) > > > Hi all, > > > > > > Commit > > > > > > db47fe727e1f ("drm/i915/step: s/<platform>_revid_tbl/<platform>_revids") > > > > > > is missing a Signed-off-by from its committer. > > > > > > -- > > > Cheers, > > > Stephen Rothwell > > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch -- Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation (916) 356-2795
WARNING: multiple messages have this Message-ID (diff)
From: Matt Roper <matthew.d.roper@intel.com> To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>, DRI <dri-devel@lists.freedesktop.org>, Intel Graphics <intel-gfx@lists.freedesktop.org>, Jani Nikula <jani.nikula@linux.intel.com>, Rodrigo Vivi <rodrigo.vivi@intel.com>, Stephen Rothwell <sfr@canb.auug.org.au>, Linux Kernel Mailing List <linux-kernel@vger.kernel.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: Mon, 9 Aug 2021 09:19:39 -0700 [thread overview] Message-ID: <20210809161939.GS1556418@mdroper-desk1.amr.corp.intel.com> (raw) In-Reply-To: <YRE2RwQ6XlUqbgmn@phenom.ffwll.local> On Mon, Aug 09, 2021 at 04:05:59PM +0200, Daniel Vetter wrote: > On Fri, Aug 06, 2021 at 09:36:56AM +0300, Joonas Lahtinen wrote: > > Hi Matt, > > > > Always use the dim tooling when applying patches, it will do the right > > thing with regards to adding the S-o-b. > > fd.o server rejects any pushes that haven't been done by dim, so how did > this get through? I definitely used dim for all of these patches, but I'm not sure how I lost my s-o-b on this one. Maybe when I edited the commit message after 'dim extract-tags' I accidentally deleted an extra line when I removed the extract-tags marker? It's the only patch where the line is missing, so it's almost certainly human error on my part rather than something dim did wrong. > Matt, can you pls figure out and type up the patch to > plug that hole? Are you referring to a patch for dim here? The i915 patch has already landed, so we can't change its commit message now. Matt > > Thanks, Daniel > > > > > Regards, Joonas > > > > Quoting Stephen Rothwell (2021-07-15 07:18:54) > > > Hi all, > > > > > > Commit > > > > > > db47fe727e1f ("drm/i915/step: s/<platform>_revid_tbl/<platform>_revids") > > > > > > is missing a Signed-off-by from its committer. > > > > > > -- > > > Cheers, > > > Stephen Rothwell > > -- > Daniel Vetter > Software Engineer, Intel Corporation > http://blog.ffwll.ch -- Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation (916) 356-2795
next prev parent reply other threads:[~2021-08-09 16:20 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-15 4:18 linux-next: Signed-off-by missing for commit in the drm-intel tree Stephen Rothwell 2021-07-15 4:18 ` [Intel-gfx] " Stephen Rothwell 2021-07-15 4:18 ` Stephen Rothwell 2021-08-06 6:36 ` Joonas Lahtinen 2021-08-06 6:36 ` [Intel-gfx] " Joonas Lahtinen 2021-08-09 14:05 ` Daniel Vetter 2021-08-09 14:05 ` [Intel-gfx] " Daniel Vetter 2021-08-09 16:19 ` Matt Roper [this message] 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 -- strict thread matches above, loose matches on Subject: below -- 2019-01-27 3:49 Stephen Rothwell 2019-01-27 3:49 ` Stephen Rothwell 2018-11-06 19:59 Stephen Rothwell 2018-11-06 19:59 ` Stephen Rothwell 2018-11-07 0:00 ` 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=20210809161939.GS1556418@mdroper-desk1.amr.corp.intel.com \ --to=matthew.d.roper@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jani.nikula@linux.intel.com \ --cc=joonas.lahtinen@linux.intel.com \ --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: linkBe 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.