From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dave Airlie <airlied@linux.ie>,
DRI <dri-devel@lists.freedesktop.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Biju Das <biju.das@bp.renesas.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the drm tree
Date: Tue, 05 Dec 2017 11:36:07 +0200 [thread overview]
Message-ID: <4577922.FDR3KI3HOI@avalon> (raw)
In-Reply-To: <20171205134550.58e1f217@canb.auug.org.au>
Hi Stephen,
On Tuesday, 5 December 2017 04:45:50 EET Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 36a46da90212 ("drm: rcar-du: Add R8A7743 support")
> cdd907001572 ("drm: rcar-du: Add R8A7745 support")
> 7912dee7775e ("drm: rcar-du: Implement system suspend/resume support")
> cf05f74ef40e ("drm: rcar-du: Remove unused CRTC suspend/resume functions")
>
> are missing a Signed-off-by from their committer.
I've sent lots of pull requests to maintainers in the past where I have picked
patches signed off by the original author without any further modification and
only added my Acked-by or Reviewed-by line. I thought this was an accepted
practice as nobody ever complained, but I'll make sure to always include my
SoB for any patch that goes through my tree in the future. I'm sorry about
this, it's all my fault.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-12-05 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 2:45 linux-next: Signed-off-by missing for commits in the drm tree Stephen Rothwell
2017-12-05 9:36 ` Laurent Pinchart [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-15 23:18 Stephen Rothwell
2018-05-17 15:27 ` Koo, Anthony
2018-03-21 9:27 Stephen Rothwell
2018-03-23 11:55 ` Tomi Valkeinen
2017-12-21 5:12 Stephen Rothwell
2017-12-21 11:40 ` Tomi Valkeinen
2017-12-21 13:06 ` Daniel Vetter
2017-12-03 23:57 Stephen Rothwell
2017-12-04 2:32 ` Zhenyu Wang
2017-08-29 1:44 Stephen Rothwell
2017-08-29 1:51 ` Sinclair Yeh
2017-08-02 6:54 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=4577922.FDR3KI3HOI@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=biju.das@bp.renesas.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--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).