From: Borislav Petkov <bp@alien8.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Tony Luck <tony.luck@intel.com>
Subject: Re: linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o)
Date: Thu, 19 May 2022 16:55:35 +0200 [thread overview]
Message-ID: <YoZaZ+HVyjKrwtSQ@zn.tnic> (raw)
In-Reply-To: <65f17e84-83e4-c33a-1718-fbb5841cef46@infradead.org>
On Wed, May 18, 2022 at 03:40:06PM -0700, Randy Dunlap wrote:
> Thanks. If you like this patch, you can add
>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
>
> to it.
Thanks.
However, the patch needs to be splitted and the IFS piece needs to go
through the platform tree. Sending them both as a reply to this message.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-05-19 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 10:29 linux-next: Tree for May 18 Stephen Rothwell
2022-05-18 21:05 ` linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o) Randy Dunlap
2022-05-18 21:34 ` Borislav Petkov
2022-05-18 21:54 ` Randy Dunlap
2022-05-18 22:29 ` Borislav Petkov
2022-05-18 22:40 ` Randy Dunlap
2022-05-19 14:55 ` Borislav Petkov [this message]
2022-05-19 14:57 ` [PATCH] platform/x86/intel/ifs: Add CPU_SUP_INTEL dependency Borislav Petkov
2022-05-19 17:47 ` Hans de Goede
2022-05-19 15:03 ` [PATCH] x86/microcode: Add explicit CPU vendor dependency Borislav Petkov
2022-05-20 9:34 ` [tip: x86/microcode] " tip-bot2 for Borislav Petkov
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=YoZaZ+HVyjKrwtSQ@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
--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.