From: Nicolas Saenz Julienne <nsaenzjulienne@suse•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the raspberrypi tree
Date: Tue, 26 Jan 2021 10:17:14 +0100 [thread overview]
Message-ID: <3f563185539b346477ca19b350d0ac8c96632398.camel@suse.de> (raw)
In-Reply-To: <20210126191117.47fffe80@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
On Tue, 2021-01-26 at 19:11 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Commits
>
> 7a5936445053 ("ARM: dts: bcm2711: Add the BSC interrupt controller")
> 69894e0baa0c ("ARM: bcm: Select BRCMSTB_L2_IRQ for bcm2835")
>
> are missing a Signed-off-by from their committer.
>
Sorry for that, I fixed the branch right away but forgot to push it.
Regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-01-26 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 8:11 linux-next: Signed-off-by missing for commit in the raspberrypi tree Stephen Rothwell
2021-01-26 9:17 ` Nicolas Saenz Julienne [this message]
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=3f563185539b346477ca19b350d0ac8c96632398.camel@suse.de \
--to=nsaenzjulienne@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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