All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the renesas tree
Date: Mon, 20 Apr 2020 13:13:39 +0200	[thread overview]
Message-ID: <CAMuHMdX8t=nQmBhNVadjV8PCOMhZP6BYZvo=zf5zZPrRSDwPgQ@mail.gmail.com> (raw)
In-Reply-To: <20200420210358.4c092dbc@canb.auug.org.au>

Hi Stephen,

On Mon, Apr 20, 2020 at 1:04 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Commit
>
>   dc7bf14a0895 ("arm64: dts: renesas: r8a77980: Fix IPMMU VIP[01] nodes")
>
> is missing a Signed-off-by from its committer.

Thank you, fixed in the fixes branch, but not in the next branch (the former
goes upstream as-is, the latter doesn't).

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2020-04-20 11:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 11:03 linux-next: Signed-off-by missing for commit in the renesas tree Stephen Rothwell
2020-04-20 11:13 ` Geert Uytterhoeven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-13 20:51 Stephen Rothwell
2023-11-14  7:49 ` Geert Uytterhoeven
2018-07-09 21:44 Stephen Rothwell
2018-07-11  7:12 ` Simon Horman
2018-04-23 21:32 Stephen Rothwell
2017-12-20 20:01 Stephen Rothwell
2017-12-21  9:21 ` Simon Horman
2017-07-27 23:21 Stephen Rothwell
2017-07-28  5:09 ` jmondi
2017-07-28  5:57   ` Stephen Rothwell
2017-07-28 19:56     ` Simon Horman

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='CAMuHMdX8t=nQmBhNVadjV8PCOMhZP6BYZvo=zf5zZPrRSDwPgQ@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.