public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: "Luck, Tony" <tony.luck@intel•com>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel•org>,
	Borislav Petkov <bp@alien8•de>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: Re: Missing signoff in the edac tree
Date: Mon, 1 Jun 2026 19:14:39 +0100	[thread overview]
Message-ID: <daedb22c-da5e-4949-8990-eaedba0c2725@sirena.org.uk> (raw)
In-Reply-To: <SJ1PR11MB6083ECFA7AEBFC7D8EE11D59FC162@SJ1PR11MB6083.namprd11.prod.outlook.com>

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

On Fri, May 29, 2026 at 10:07:35PM +0000, Luck, Tony wrote:
> > Commit

> >  3b48fd01d94cd ("EDAC: Consistently define pci_device_ids using named initializers")

> > is missing a Signed-off-by from its committer

> Boris pointed this out to me earlier today.  Updated that commit (top one in edac-drivers branch)

> New SHA1:

> 78d86a71de6e ("EDAC: Consistently define pci_device_ids using named initializers")

I'm still seeing the old merge in the history (8b3604b9e3eb47df), the
new one is there too.  Probably fine but that's up to Linus.

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

  reply	other threads:[~2026-06-01 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 21:57 Missing signoff in the edac tree Mark Brown
2026-05-29 22:07 ` Luck, Tony
2026-06-01 18:14   ` Mark Brown [this message]
2026-06-01 18:20     ` Borislav Petkov

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=daedb22c-da5e-4949-8990-eaedba0c2725@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=bp@alien8$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mchehab+samsung@kernel$(echo .)org \
    --cc=tony.luck@intel$(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