All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Arnd Bergmann <arnd@kernel.org>,
	Tony Krowiak <akrowiak@linux.ibm.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Arnd Bergmann <arnd@arndb.de>,
	"Steven Rostedt (Google)" <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: Thu, 26 Jan 2023 10:45:15 -0700	[thread overview]
Message-ID: <20230126104515.3fcb3abf.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230126174044.GA15999@lst.de>

On Thu, 26 Jan 2023 18:40:44 +0100
Christoph Hellwig <hch@lst.de> wrote:

> On Thu, Jan 26, 2023 at 10:38:11AM -0700, Alex Williamson wrote:
> > Seems like it wouldn't just be the sample drivers with this issue,
> > don't VFIO_CCW, VFIO_AP, and DRM_I915_GVT_KVMGT all have this problem?
> > Thanks,  
> 
> Yes, they all need to depend on VFIO.
> 
> Should I resend the series with that fixed?

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,

Alex


  reply	other threads:[~2023-01-26 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 16:37 [PATCH] vfio-mdev: add back CONFIG_VFIO dependency Arnd Bergmann
2023-01-26 17:38 ` Alex Williamson
2023-01-26 17:40   ` Christoph Hellwig
2023-01-26 17:45     ` Alex Williamson [this message]
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

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=20230126104515.3fcb3abf.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 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.