public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Gross <agross@kernel•org>, Arnd Bergmann <arnd@arndb•de>
Cc: Bjorn Andersson <andersson@kernel•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	ARM <linux-arm-kernel@lists•infradead.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the qcom tree
Date: Fri, 17 Jan 2025 07:20:15 +1100	[thread overview]
Message-ID: <20250117072015.77bf3589@canb.auug.org.au> (raw)
In-Reply-To: <20250106064548.0a2b62c3@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

Hi all,

On Mon, 6 Jan 2025 06:45:48 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Commit
> 
>   3d0d8c8989d3 ("arm64: dts: qcom: qcs8300: Add watchdog node")
> 
> is missing a Signed-off-by from its committer.

This commit is now in the arm-soc tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-01-16 20:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 19:45 linux-next: Signed-off-by missing for commit in the qcom tree Stephen Rothwell
2025-01-16 20:20 ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-14  6:01 Stephen Rothwell
2025-11-14 14:52 ` Bjorn Andersson
2025-08-11 22:12 Stephen Rothwell
2025-07-17 21:53 Stephen Rothwell
2023-01-31  5:11 Stephen Rothwell
2023-01-31 12:28 ` Georgi Djakov
2023-01-11 21:12 Stephen Rothwell
2020-11-24  7:19 Stephen Rothwell
2020-11-24 14:14 ` Bjorn Andersson
2019-09-01 21:20 Stephen Rothwell
2019-04-25 12:54 Stephen Rothwell
2018-05-14 21:26 Stephen Rothwell
2018-04-25 21:33 Stephen Rothwell

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=20250117072015.77bf3589@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=agross@kernel$(echo .)org \
    --cc=andersson@kernel$(echo .)org \
    --cc=arnd@arndb$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.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