RE: [RFC PATCH v4 02/24] Update linux-header per VFIO device cdev v14

[Cornelia Huck]

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.