Re: [Qemu-devel] [PATCH v12 3/4] headers: Update kernel header

[Alexander Graf <agraf@suse.de>]

On 16.07.14 03:40, Gavin Shan wrote:
> On Wed, Jul 16, 2014 at 11:32:13AM +1000, Alexey Kardashevskiy wrote:
>> On 07/16/2014 11:16 AM, Gavin Shan wrote:
>>> On Wed, Jul 16, 2014 at 11:09:44AM +1000, Alexey Kardashevskiy wrote:
>>>> On 07/16/2014 10:20 AM, Gavin Shan wrote:
>>>>> This updates kernel header (vfio.h) for EEH support on VFIO PCI
>>>>> devices.
>>>> Has this reached kernel upstream? The way linux headers update normally
>>>> happens is you have to run scripts/update-linux-headers.sh against some
>>>> linux kernel tag which you know that it won't change (like v3.16-rc5) and
>>>> post all the changes as a single patch. It is never a header update for a
>>>> specific feature, it is just an update.
>>>>
>>> The kernel part isn't merged yet. I guess that's for 3.17 merge window.
>>> Ok, good to know scripts/update-linux-headers.sh. So this patch should
>>> be dropped and some one run the script to update QEMU (linux-headers
>>> directory) ?
>>
>> Once your changes are in upstream kernel, you wait till kernel tree gets
>> new "v3.xx-rcX" tag, then you run the script and make a separate patch for
>> QEMU. Then you wait till it reaches QEMU upstream (because I do not know
>> who will pull it to what tree, look at git history) or ppc-next (if Alex
>> pulls it and you are basing your work on ppc-next) and then repost other
>> patches.
>>
> Thanks for detailed explaining, Alexey. I guess I have to suspend a bit
> until "v3.17.rc1" is coming out.

It's also perfectly fine to keep the kernel header update inside your 
patch set, but please make sure to mention which commit it is against. 
If I pick it up, I will generate the headers myself though and drop your 
patch while applying the rest of the set.


Alex