public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jon Kohler <jon@nutanix.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Tony Krowiak <akrowiak@linux.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Rohit Shenoy <rshenoy@nvidia.com>,
	Tarun Gupta <targupta@nvidia.com>
Subject: Re: [PATCH] vfio-mdev: reinstate VFIO_MDEV Kconfig
Date: Mon, 16 Sep 2024 09:20:30 +0200	[thread overview]
Message-ID: <20240916072030.GC16514@lst.de> (raw)
In-Reply-To: <8A26B654-51D0-4007-919C-F1934BD0DFEE@nutanix.com>

On Thu, Sep 12, 2024 at 03:32:52PM +0000, Jon Kohler wrote:
> Christoph - thanks for the swift reply, I appreciate it. To clarify slightly,
> MDEV does have various exported symbols in MDEV, with both regular
> EXPORT_SYMBOL and _GPL variant; however, there is just no way to 
> consume them out of tree without this patch, unless there is also
> incidentally another in-tree module that has select VFIO_MDEV set.

The point of kernel infrastructure is not to consume it out of tree.
Get your driver upstream and fully participate instead wasting your
time on this kind of stuff please.

      reply	other threads:[~2024-09-16  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 14:19 [PATCH] vfio-mdev: reinstate VFIO_MDEV Kconfig Jon Kohler
2024-09-12 14:05 ` Christoph Hellwig
2024-09-12 15:32   ` Jon Kohler
2024-09-16  7:20     ` Christoph Hellwig [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=20240916072030.GC16514@lst.de \
    --to=hch@lst.de \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=jon@nutanix.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rshenoy@nvidia.com \
    --cc=targupta@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox