linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Luo <luoben@linux.alibaba.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: linux-kernel@vger.kernel.org, tao.ma@linux.alibaba.com,
	gerry@linux.alibaba.com, nanhai.zou@linux.alibaba.com
Subject: Re: [PATCH v6 0/3] genirq/vfio: Introduce irq_update_devid() and optimize VFIO irq ops
Date: Thu, 5 Dec 2019 18:12:41 +0800	[thread overview]
Message-ID: <8e7961d5-c27e-4921-45ff-af8cc8946ac3@linux.alibaba.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1909161615230.1887@nanos.tec.linutronix.de>

Hi Thomas,

Could you please take a look at this again, just a friendly reminder :)

Thanks,

     Ben

在 2019/9/16 下午10:16, Thomas Gleixner 写道:
> On Fri, 13 Sep 2019, Alex Williamson wrote:
>
>> On Tue, 10 Sep 2019 14:30:16 +0800
>> Ben Luo <luoben@linux.alibaba.com> wrote:
>>
>>> A friendly reminder.
>> The vfio patch looks ok to me.  Thomas, do you have further comments or
>> a preference on how to merge these?  I'd tend to prefer the vfio
>> changes through my branch for testing and can pull the irq changes with
>> your approval, but we could do the reverse or split them and I could
>> follow with the vfio change once the irq changes are in mainline.
> I can provide you a branch, once I looked again at that stuff. It's
> somewhere in that huge conference induced backlog.
>
> Thanks,
>
> 	tglx

      reply	other threads:[~2019-12-05 10:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  4:01 [PATCH v6 0/3] genirq/vfio: Introduce irq_update_devid() and optimize VFIO irq ops Ben Luo
2019-09-02  4:01 ` [PATCH v6 1/3] genirq: enhance error recovery code in free irq Ben Luo
2019-09-02  4:01 ` [PATCH v6 2/3] genirq: introduce irq_update_devid() Ben Luo
2019-09-02  4:01 ` [PATCH v6 3/3] vfio/pci: make use of irq_update_devid() and optimize irq ops Ben Luo
2019-09-10  6:30 ` [PATCH v6 0/3] genirq/vfio: Introduce irq_update_devid() and optimize VFIO " Ben Luo
2019-09-13 17:44   ` Alex Williamson
2019-09-16 14:16     ` Thomas Gleixner
2019-12-05 10:12       ` Ben Luo [this message]

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=8e7961d5-c27e-4921-45ff-af8cc8946ac3@linux.alibaba.com \
    --to=luoben@linux.alibaba.com \
    --cc=alex.williamson@redhat.com \
    --cc=gerry@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nanhai.zou@linux.alibaba.com \
    --cc=tao.ma@linux.alibaba.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).