public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alasdair G Kergon <agk@redhat•com>, Mike Snitzer <snitzer@redhat•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 device-mapper tree
Date: Tue, 16 Jan 2018 00:27:36 +1100	[thread overview]
Message-ID: <20180116002736.4d464214@canb.auug.org.au> (raw)

Hi all,

Commit

  34e1467da673 ("Revert "genirq/affinity: assign vectors to all possible CPUs"")

is missing a Signed-off-by from its author and committer.

Reverts are commits as well.

Though I do note it actually has a reasonable commit message, thanks.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2018-01-15 13:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15 13:27 Stephen Rothwell [this message]
2018-01-15 15:25 ` 4.16 genirq change prevents HP servers from booting [was: Re: linux-next: Signed-off-by missing for commit in the device-mapper tree] Mike Snitzer
2018-01-15 15:33   ` Ming Lei
  -- strict thread matches above, loose matches on Subject: below --
2018-01-25 11:15 linux-next: Signed-off-by missing for commit in the device-mapper tree Stephen Rothwell
2018-12-06 22:47 Stephen Rothwell
2020-11-18 20:47 Stephen Rothwell
2020-11-18 21:19 ` Mike Snitzer
2021-05-26 21:59 Stephen Rothwell
2023-11-29 20:36 Stephen Rothwell
2024-03-03 22:15 Stephen Rothwell
2024-03-12 21:05 Stephen Rothwell
2024-07-08  8:20 Stephen Rothwell
2024-07-08 13:00 ` Mikulas Patocka
2024-07-11 22:38 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=20180116002736.4d464214@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=agk@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=snitzer@redhat$(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