All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Rei Yamamoto <yamamoto.rei@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, ming.lei@redhat.com
Subject: Re: [PATCH v3] irq: consider cpus on nodes are unbalanced
Date: Thu, 31 Mar 2022 01:09:03 +0200	[thread overview]
Message-ID: <87zgl7m41c.ffs@tglx> (raw)
In-Reply-To: <20220330044254.15712-1-yamamoto.rei@jp.fujitsu.com>

On Wed, Mar 30 2022 at 13:42, Rei Yamamoto wrote:
> On Thu, Feb 10, 2022 at 12:10:18PM +0800, Ming Lei wrote:
>> On Thu, Feb 10, 2022 at 12:10:53PM +0900, Rei Yamamoto wrote:
>
> Could you pick this patch up?

Which patch? Whatever that patch is, it did neither arrive in my inbox
nor in a public archive:

    https://lore.kernel.org/all/20220210031053.5352-1-yamamoto.rei@jp.fujitsu.com/

Thanks,

        tglx

  reply	other threads:[~2022-03-30 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220210031053.5352-1-yamamoto.rei@jp.fujitsu.com>
2022-02-10  4:10 ` [PATCH v3] irq: consider cpus on nodes are unbalanced Ming Lei
2022-03-30  4:42   ` Rei Yamamoto
2022-03-30 23:09     ` Thomas Gleixner [this message]
2022-03-31  0:24       ` Rei Yamamoto

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=87zgl7m41c.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=yamamoto.rei@jp.fujitsu.com \
    /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.