public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"clg@redhat.com" <clg@redhat.com>,
	"jgg@nvidia.com" <jgg@nvidia.com>,
	"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
	"eric.auger@redhat.com" <eric.auger@redhat.com>,
	"peterx@redhat.com" <peterx@redhat.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"Liu, Yi L" <yi.l.liu@intel.com>,
	"Sun, Yi Y" <yi.y.sun@intel.com>,
	"Peng, Chao P" <chao.p.peng@intel.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"open list:Overall KVM CPUs" <kvm@vger.kernel.org>
Subject: RE: [RFC PATCH v4 02/24] Update linux-header per VFIO device cdev v14
Date: Wed, 12 Jul 2023 11:35:48 +0200	[thread overview]
Message-ID: <87sf9tjwuj.fsf@redhat.com> (raw)
In-Reply-To: <PH7PR11MB67221F2DE29B1995918B94159236A@PH7PR11MB6722.namprd11.prod.outlook.com>

On Wed, Jul 12 2023, "Duan, Zhenzhong" <zhenzhong.duan@intel.com> wrote:

>>-----Original Message-----
>>From: Cornelia Huck <cohuck@redhat.com>
>>Sent: Wednesday, July 12, 2023 3:49 PM
>>Subject: Re: [RFC PATCH v4 02/24] Update linux-header per VFIO device cdev
>>v14
>>
>>On Wed, Jul 12 2023, Zhenzhong Duan <zhenzhong.duan@intel.com> wrote:
>>
>>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
>>> ---
>>>  linux-headers/linux/iommufd.h | 347
>>++++++++++++++++++++++++++++++++++
>>>  linux-headers/linux/kvm.h     |  13 +-
>>>  linux-headers/linux/vfio.h    | 142 +++++++++++++-
>>>  3 files changed, 498 insertions(+), 4 deletions(-)
>>>  create mode 100644 linux-headers/linux/iommufd.h
>>
>>Hi,
>>
>>if this patch is intending to pull code that is not yet integrated in
>>the Linux kernel, please mark this as a placeholder patch. If the code
>>is already integrated, please run a full headers update against a
>>released version (can be -rc) and note that version in the patch
>>description.
> Thanks for point out, will do in next post.
> About "placeholder patch", should I claim it is placeholder in patch
> subject or description field, or there is official step to do that?

Just put a notice into the subject and/or the patch description; the
main idea is to prevent a maintainer from applying it by accident.


  reply	other threads:[~2023-07-12  9:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230712072528.275577-1-zhenzhong.duan@intel.com>
2023-07-12  7:25 ` [RFC PATCH v4 02/24] Update linux-header per VFIO device cdev v14 Zhenzhong Duan
2023-07-12  7:49   ` Cornelia Huck
2023-07-12  9:28     ` Duan, Zhenzhong
2023-07-12  9:35       ` Cornelia Huck [this message]
2023-07-12  9:50         ` Duan, Zhenzhong

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=87sf9tjwuj.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=chao.p.peng@intel.com \
    --cc=clg@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=nicolinc@nvidia.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yi.l.liu@intel.com \
    --cc=yi.y.sun@intel.com \
    --cc=zhenzhong.duan@intel.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