public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 17:12:49 +0100	[thread overview]
Message-ID: <Y7MCgS9Ix7qcLdct@zn.tnic> (raw)
In-Reply-To: <CAHmME9rMTNQ+hZPG1cbpP2zA6Cq3-f=gXXPF3=WYhQWicEYV4w@mail.gmail.com>

On Mon, Jan 02, 2023 at 04:59:08PM +0100, Jason A. Donenfeld wrote:
> Rest of series is intended to go through random.git tree, so it'd be
> useful to not have to carry this there -- less pain.

Ping me when the time has come and I'll ack it so that it can go through the
random.git tree too. Provided there are no serious conflicts but we'll cross
that bridge when we get to it...

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2023-01-02 16:13 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
2023-01-02 15:59               ` Jason A. Donenfeld
2023-01-02 16:12                 ` Borislav Petkov [this message]
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=Y7MCgS9Ix7qcLdct@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