All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: SoC Team <soc@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] ARM: SoC fixes for v5.18, part 4
Date: Wed, 18 May 2022 14:10:50 -1000	[thread overview]
Message-ID: <CAHk-=whdu=QVt=_rviX-5-txb4haxNW-zTc8cFpjsjsemt72QA@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3V3voFgDz+yQji9PpVNs=QOj8MEtdaFf1U3JrLSG6SmQ@mail.gmail.com>

On Wed, May 18, 2022 at 7:19 AM Arnd Bergmann <arnd@kernel.org> wrote:
>
> I'm sorry for the lack of a signed tag this time, I'm travelling at
> the moment and
> forgot to tag it first. The top commit in the branch is tagged with my
> usual key,
> and I can send the signed tag when I'm back on Saturday if you prefer to wait.

I've tried to encourage everybody to use signed tags, but for
kernel.org pulls it's not like it's a hard requirement, so no worries.

               Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: SoC Team <soc@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] ARM: SoC fixes for v5.18, part 4
Date: Wed, 18 May 2022 14:10:50 -1000	[thread overview]
Message-ID: <CAHk-=whdu=QVt=_rviX-5-txb4haxNW-zTc8cFpjsjsemt72QA@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a3V3voFgDz+yQji9PpVNs=QOj8MEtdaFf1U3JrLSG6SmQ@mail.gmail.com>

On Wed, May 18, 2022 at 7:19 AM Arnd Bergmann <arnd@kernel.org> wrote:
>
> I'm sorry for the lack of a signed tag this time, I'm travelling at
> the moment and
> forgot to tag it first. The top commit in the branch is tagged with my
> usual key,
> and I can send the signed tag when I'm back on Saturday if you prefer to wait.

I've tried to encourage everybody to use signed tags, but for
kernel.org pulls it's not like it's a hard requirement, so no worries.

               Linus

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-19  0:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 17:19 [GIT PULL] ARM: SoC fixes for v5.18, part 4 Arnd Bergmann
2022-05-18 17:19 ` Arnd Bergmann
2022-05-19  0:10 ` Linus Torvalds [this message]
2022-05-19  0:10   ` Linus Torvalds
2022-05-19  0:35 ` pr-tracker-bot
2022-05-19  0:35   ` pr-tracker-bot

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='CAHk-=whdu=QVt=_rviX-5-txb4haxNW-zTc8cFpjsjsemt72QA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=arnd@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@kernel.org \
    /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.