linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Walmsley <paul@pwsan.com>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: linux-next: Signed-off-by missing for commit in the risc-v tree
Date: Thu, 27 Oct 2022 14:47:06 -0700 (PDT)	[thread overview]
Message-ID: <mhng-f863de75-c99d-4fca-96c0-e2d5eb380916@palmer-ri-x1c9a> (raw)
In-Reply-To: <20221028063027.362963bb@canb.auug.org.au>

On Thu, 27 Oct 2022 12:30:27 PDT (-0700), Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
>   b2ea3c7a7d21 ("RISC-V: Cache SBI vendor values")
>
> is missing a Signed-off-by from its committer.

Sorry about that, this should be fixed.

  reply	other threads:[~2022-10-27 21:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 19:30 linux-next: Signed-off-by missing for commit in the risc-v tree Stephen Rothwell
2022-10-27 21:47 ` Palmer Dabbelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-02 20:55 Stephen Rothwell
2023-11-02 21:02 ` Palmer Dabbelt
2023-08-30 21:57 Stephen Rothwell
2023-09-01 16:14 ` Palmer Dabbelt
2023-01-18  4:10 Stephen Rothwell
2023-01-18  4:16 ` Palmer Dabbelt
2021-10-04 21:09 Stephen Rothwell
2021-10-04 22:29 ` Palmer Dabbelt
2021-08-26 21:12 Stephen Rothwell
2021-04-25  3:01 Stephen Rothwell
2021-04-26 16:07 ` Palmer Dabbelt
2020-11-08 21:18 Stephen Rothwell
2020-07-11 23:35 Stephen Rothwell
2020-06-06  1:14 Stephen Rothwell
2020-03-31 20:52 Stephen Rothwell
2020-01-30 20:17 Stephen Rothwell
2020-02-05 22:09 ` Palmer Dabbelt
2019-05-08 21:47 Stephen Rothwell
2019-05-08 22:15 ` Palmer Dabbelt
2018-08-05 21:37 Stephen Rothwell
2018-08-06 22:49 ` Palmer Dabbelt

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=mhng-f863de75-c99d-4fca-96c0-e2d5eb380916@palmer-ri-x1c9a \
    --to=palmer@dabbelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).