All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/urgent for 6.1
Date: Sun, 23 Oct 2022 11:54:42 +0200	[thread overview]
Message-ID: <Y1UPYnju4qOTsusI@zn.tnic> (raw)
In-Reply-To: <Y1ULKYsASLRoVb7N@zn.tnic>

On Sun, Oct 23, 2022 at 11:36:41AM +0200, Borislav Petkov wrote:
> Hi Linus,
> 
> as it is usually the case, right after a major release, the tip urgent
> branches accumulate a couple more fixes than normal. And here is the
> x86, a bit bigger, urgent pile.
> 
> Please pull,
> thx.
> 
> ---
> 
> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
> 
>   Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v6.0_rc2
									          ^^^^^

Whoops, I mistyped the version in the tag. Lemme know if you need a
properly renamed tag: x86_urgent_for_v6.1_rc2

Thx.

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)

  reply	other threads:[~2022-10-23  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23  9:36 [GIT PULL] x86/urgent for 6.1 Borislav Petkov
2022-10-23  9:54 ` Borislav Petkov [this message]
2022-10-23 17:06   ` Linus Torvalds
2022-10-23 18:14     ` Borislav Petkov
2022-10-23 18:42       ` Linus Torvalds
2022-10-23 19:06         ` Borislav Petkov
2022-10-23 17:18 ` 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=Y1UPYnju4qOTsusI@zn.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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.