public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: Signed-off-by missing for commits in the arm-soc tree
Date: Mon, 16 Jul 2018 07:57:18 +1000	[thread overview]
Message-ID: <20180716075718.4e5ef491@canb.auug.org.au> (raw)

Hi all,

Commits

  b8ccf02a5014 ("ARM: dts: bcm283x: Add the PMU to the devicetree.")
  b7dd29b401f5 ("ARM: dts: bcm283x: Add Transposer block")
  74d1e007915f ("hwmon: Add support for RPi voltage sensor")
  70eea1bbb556 ("firmware: raspberrypi: Register hwmon driver")
  a1547e0bca51 ("firmware: raspberrypi: Remove VLA usage")

are missing a Signed-off-by from their committer.

-- 
Cheers,
Stephen Rothwell
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180716/752046b0/attachment.sig>

             reply	other threads:[~2018-07-15 21:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15 21:57 Stephen Rothwell [this message]
2018-07-15 22:50 ` linux-next: Signed-off-by missing for commits in the arm-soc tree Olof Johansson
2018-07-16  9:13   ` Florian Fainelli
2018-07-16  9:24     ` Chen-Yu Tsai
2018-07-16  9:54       ` Florian Fainelli
2018-07-16  9:57       ` Russell King - ARM Linux
2018-07-16 11:55         ` Florian Fainelli
  -- strict thread matches above, loose matches on Subject: below --
2018-10-02 21:21 Stephen Rothwell
2018-10-04 19:37 ` Maxime Ripard
2020-07-26 21:35 Stephen Rothwell
2020-07-27  7:27 ` Arnd Bergmann
2021-10-27 11:53 Stephen Rothwell
2022-02-27 20:45 Stephen Rothwell
2022-02-28 11:53 ` Arnd Bergmann

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=20180716075718.4e5ef491@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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