From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dave Airlie <airlied@linux•ie>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
CK Hu <ck.hu@mediatek•com>, YT Shen <yt.shen@mediatek•com>,
shaoming chen <shaoming.chen@mediatek•com>,
Rob Herring <robh@kernel•org>
Subject: linux-next: missing signatures on commits in the drm tree
Date: Tue, 11 Apr 2017 07:50:23 +1000 [thread overview]
Message-ID: <20170411075023.3bf147de@canb.auug.org.au> (raw)
Hi Dave,
I noticed that a series of commits in the drm tree
(git://people.freedesktop.org/~airlied/linux.git#drm-next) do not have
Signed-off-by tags from their committer - they have Acked-by tags instead:
84a5ead18e57 drm/mediatek: add support for Mediatek SoC MT2701
0707632b5bac drm/mediatek: update DSI sub driver flow for sending commands to panel
2d52bfba09d1 drm/mediatek: add non-continuous clock mode and EOT packet control
21898816831f drm/mediatek: add dsi transfer function
dd5080a54df8 drm/mediatek: add dsi interrupt control
80a5cfd60d2a drm/mediatek: cleaning up and refine
fb2557de27e3 drm/mediatek: update display module connections
c37813de6687 drm/mediatek: add BLS component
9dc84e98a31f drm/mediatek: add shadow register support
c5f228ef6ccd drm/mediatek: add *driver_data for different hardware settings
55dc065e3ec6 drm/mediatek: add helpers for coverting from the generic components
e3215713f878 dt-bindings: display: mediatek: update supported chips
This last one doesn't even have an Acked-by from its committer.
--
Cheers,
Stephen Rothwell
reply other threads:[~2017-04-10 21:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170411075023.3bf147de@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=airlied@linux$(echo .)ie \
--cc=ck.hu@mediatek$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
--cc=shaoming.chen@mediatek$(echo .)com \
--cc=yt.shen@mediatek$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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