From: Borislav Petkov <bp@alien8.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86: lib: Separate instruction decoder MMIO type from MMIO trace
Date: Mon, 2 Jan 2023 16:30:39 +0100 [thread overview]
Message-ID: <Y7L4n0imic1ncHhe@zn.tnic> (raw)
In-Reply-To: <CAHmME9ojkPUV-acD8o1rFsfR+f7URG8PW44GUUt8WUK0O=KD6w@mail.gmail.com>
On Mon, Jan 02, 2023 at 03:49:23PM +0100, Jason A. Donenfeld wrote:
> Do you think you could queue up this patch for 6.2 as a fix? It has
> basically no chance of breakage and does fix a real symbol clash.
>
> https://lore.kernel.org/lkml/20221214203454.337299-1-Jason@zx2c4.com/
>
> This doesn't fix any existing compile error that I'm aware of, but if
> this makes it into 6.2, it would avoid me having to carry it in a series
> I'm working on,...
Our general rule for urgent fixes going through tip is that they should qualify
to be CC:stable fixes. And this one isn't so I think you should hold on to it
and submit it along with the whole series as it is usually done.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2023-01-02 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 21:02 [PATCH] x86: lib: Separate instruction decoder MMIO type from MMIO trace Jason A. Donenfeld
2022-12-14 19:56 ` Ricardo Neri
2022-12-14 20:32 ` Jason A. Donenfeld
2022-12-14 20:34 ` [PATCH v2] " Jason A. Donenfeld
2022-12-14 21:30 ` Ricardo Neri
2022-12-16 20:13 ` Jason A. Donenfeld
2023-01-02 14:49 ` Jason A. Donenfeld
2023-01-02 15:30 ` Borislav Petkov [this message]
2023-01-02 15:59 ` Jason A. Donenfeld
2023-01-02 16:12 ` Borislav Petkov
2023-01-02 16:14 ` Jason A. Donenfeld
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=Y7L4n0imic1ncHhe@zn.tnic \
--to=bp@alien8.de \
--cc=Jason@zx2c4.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox