From: Cornelia Huck <cohuck@redhat.com>
To: Albert Esteve <aesteve@redhat.com>,
Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
Vikram Garhwal <vikram.garhwal@bytedance.com>,
Jason Wang <jasowang@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Francisco Iglesias <francisco.iglesias@amd.com>,
Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: Re: [RFC 1/2] linux-headers: add virtio_can.h
Date: Fri, 31 Oct 2025 17:33:39 +0100 [thread overview]
Message-ID: <87seezrpy4.fsf@redhat.com> (raw)
In-Reply-To: <CADSE00Kt673u5OngA+teDO3fKcc-uBOoFKyF==U0zv1JDqC4wA@mail.gmail.com>
On Fri, Oct 31 2025, Albert Esteve <aesteve@redhat.com> wrote:
> On Fri, Oct 31, 2025 at 5:00 PM Matias Ezequiel Vara Larsen
> <mvaralar@redhat.com> wrote:
>>
>> Signed-off-by: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
>> ---
>> Note that virtio_can.h is not merged yet and it is part of the series
>> https://lore.kernel.org/all/aQJRnX7OpFRY%2F1+H@fedora/
>
> Hi Matias,
>
> As far as I know, standard-headers must be updated with
> `./scripts/update-linux-headers.sh`, so unless exceptions can be it'll
> have to wait until the kernel patch is merged for this to be accepted.
It's fine to have it as a placeholder patch for review (this series is
marked as RFC anyway) -- I'd recommend to put "Placeholder for headers
update, do not merge" more prominently in there, though.
prev parent reply other threads:[~2025-10-31 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 15:56 [RFC 1/2] linux-headers: add virtio_can.h Matias Ezequiel Vara Larsen
2025-10-31 15:56 ` [RFC 2/2] Add vhost-user-can and vhost-user-can-pci devices Matias Ezequiel Vara Larsen
2025-10-31 16:15 ` [RFC 1/2] linux-headers: add virtio_can.h Albert Esteve
2025-10-31 16:33 ` Cornelia Huck [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=87seezrpy4.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=aesteve@redhat.com \
--cc=francisco.iglesias@amd.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pisa@cmp.felk.cvut.cz \
--cc=qemu-devel@nongnu.org \
--cc=vikram.garhwal@bytedance.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 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.