mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Christoph Hellwig" <hch@lst.de>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Tony Krowiak" <akrowiak@linux.ibm.com>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Finn Behrens" <me@kloenk.de>, "Miguel Ojeda" <ojeda@kernel.org>,
	"Masami Hiramatsu" <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vfio-mdev: add back CONFIG_VFIO dependency
Date: Mon, 30 Jan 2023 12:32:54 -0700	[thread overview]
Message-ID: <20230130123254.5f69f917.alex.williamson@redhat.com> (raw)
In-Reply-To: <a870060c-9438-4383-97e3-e77d1c361b51@app.fastmail.com>

On Mon, 30 Jan 2023 14:34:54 +0100
"Arnd Bergmann" <arnd@arndb.de> wrote:

> On Mon, Jan 30, 2023, at 08:33, Christoph Hellwig wrote:
> > On Thu, Jan 26, 2023 at 10:45:15AM -0700, Alex Williamson wrote:  
> >> The culprit is already in my next branch, we just need a fix that
> >> includes all the cases.  A respin of Arnd's patch would be preferable
> >> to keep the fixes in one place.  Thanks,  
> >
> > Arnd, do you plan to resend the patch, or should I take care of it?  
> 
> I sent the v2 last week, it looks like I forgot to add you to Cc there:
> 
> https://lore.kernel.org/all/20230126211211.1762319-1-arnd@kernel.org/

Thanks for the v2, Arnd.  Last call for any acks on the above, this is
setting off too many build failures.  Thanks,

Alex


      parent reply	other threads:[~2023-01-30 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 16:37 Arnd Bergmann
2023-01-26 17:38 ` Alex Williamson
2023-01-26 17:40   ` Christoph Hellwig
2023-01-26 17:45     ` Alex Williamson
2023-01-30  7:33       ` Christoph Hellwig
2023-01-30 13:34         ` Arnd Bergmann
2023-01-30 13:39           ` Arnd Bergmann
2023-01-30 13:44             ` Jason Gunthorpe
2023-01-30 19:32           ` Alex Williamson [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=20230130123254.5f69f917.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=hch@lst.de \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@kloenk.de \
    --cc=mhiramat@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®