From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Nicolas Ferre <nicolas.ferre@atmel•com>,
Alexandre Belloni <alexandre.belloni@bootlin•com>,
Ludovic Desroches <ludovic.desroches@microchip•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: linux-next: Signed-off-by missing for commit in the at91 tree
Date: Thu, 28 Mar 2019 07:31:25 +1100 [thread overview]
Message-ID: <20190328073125.0e5a5668@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
Hi all,
Commits
080eb452bdc8 ("ARM: dts: at91: sama5d2_xplained: Add proper regulator states for suspend-to-mem")
2802bac0b675 ("ARM: dts: at91: sama5d2: add labels to soc dtsi for derivative boards")
0c0fccec0545 ("ARM: at91: pm: do not disable/enable PLLA for ULP modes")
9e35b518b8b2 ("ARM: at91: pm: disable RC oscillator in ULP0")
1b86244a4d5e ("ARM: at91: pm: add ULP1 support for SAM9X60")
0017bace228b ("ARM: at91: pm: add support for per SoC wakeup source configuration")
3201145a666b ("ARM: at91: pm: keep at91_pm_backup_init() only for SAMA5D2 SoCs")
24c2ac08869b ("ARM: at91: pm: initial PM support for SAM9X60")
0b072b0e1bd6 ("dt-bindings: arm: atmel: add binding for SAM9X60 SoC")
783d37b06ad4 ("ARM: at91: pm: introduce at91_soc_pm structure")
are missing a Signed-off-by from their committers.
Rebasing will do that ...
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-03-27 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 20:31 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-06 20:14 linux-next: Signed-off-by missing for commit in the at91 tree Stephen Rothwell
2023-07-31 5:06 Stephen Rothwell
2025-05-12 21:29 Stephen Rothwell
2025-05-13 7:31 ` Claudiu Beznea
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=20190328073125.0e5a5668@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alexandre.belloni@bootlin$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ludovic.desroches@microchip$(echo .)com \
--cc=nicolas.ferre@atmel$(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