From: Peter Xu <peterx@redhat.com>
To: Juan Quintela <quintela@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org,
"Leonardo Bras Soares Passos" <lsoaresp@redhat.com>,
"Michal Prívozník" <mprivozn@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v2 1/3] linux-headers: Update to v6.1
Date: Thu, 2 Feb 2023 14:49:20 -0500 [thread overview]
Message-ID: <Y9wTwCAwWRmHdc/a@x1n> (raw)
In-Reply-To: <878rhgtk29.fsf@secure.mitica>
On Thu, Feb 02, 2023 at 11:53:34AM +0100, Juan Quintela wrote:
> Peter Xu <peterx@redhat.com> wrote:
> > Signed-off-by: Peter Xu <peterx@redhat.com>
>
> How does this change gets into the tree?
>
> I know that it is "automagically" generated, but who decides when that
> goes into the tree?
>
> As we need that for the following patch?
Copy PeterM. Peter, could you share how we used to do linux header
updates?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-02-02 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 21:10 [PATCH v2 0/3] util/userfaultfd: Support /dev/userfaultfd Peter Xu
2023-02-01 21:10 ` [PATCH v2 1/3] linux-headers: Update to v6.1 Peter Xu
2023-02-02 10:53 ` Juan Quintela
2023-02-02 19:49 ` Peter Xu [this message]
2023-02-01 21:10 ` [PATCH v2 2/3] util/userfaultfd: Add uffd_open() Peter Xu
2023-02-02 10:27 ` Juan Quintela
2023-02-01 21:10 ` [PATCH v2 3/3] util/userfaultfd: Support /dev/userfaultfd Peter Xu
2023-02-02 10:52 ` Juan Quintela
2023-02-02 20:41 ` Peter Xu
2023-02-03 21:01 ` Juan Quintela
2023-02-06 21:31 ` Peter Xu
2023-02-07 0:11 ` Juan Quintela
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=Y9wTwCAwWRmHdc/a@x1n \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=mprivozn@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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;
as well as URLs for NNTP newsgroup(s).