From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linus Walleij <linus.walleij@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: Signed-off-bys missing for commits in the pinctrl tree
Date: Fri, 13 Sep 2019 01:02:20 +1000 [thread overview]
Message-ID: <20190913010220.087c906d@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
Hi all,
Commits
5a85bd8e3af3 ("pinctrl: meson-gxbb: Fix wrong pinning definition for uart_c")
235e8677e92b ("pinctrl: mediatek: Add support for pin configuration dump via debugfs.")
dbe733ac908e ("pinctrl: mediatek: Backward compatible to previous Mediatek's bias-pull usage")
7ed13ac1a968 ("pinctrl: mediatek: Refine mtk_pinconf_get() and mtk_pinconf_set()")
56d1a061f882 ("pinctrl: mediatek: Supporting driving setting without mapping current to register value")
319b83e60069 ("pinctrl: mediatek: Check gpio pin number and use binary search in mtk_hw_pin_field_lookup()")
are missing a Signed-off-by from their authors.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2019-09-12 15:02 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=20190913010220.087c906d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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