qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: maobibo <maobibo@loongson.cn>, Thomas Huth <thuth@redhat.com>,
	gaosong <gaosong@loongson.cn>,
	Tianrui Zhao <zhaotianrui@loongson.cn>,
	qemu-devel@nongnu.org, mst@redhat.com,
	Peter Maydell <peter.maydell@linaro.org>,
	Richard Henderson <richard.henderson@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	lixianglai@loongson.cn
Subject: Re: [PATCH] linux-headers: Synchronize linux headers from linux v6.7.0-rc1
Date: Fri, 17 Nov 2023 07:35:25 +0100	[thread overview]
Message-ID: <800a75b9-8c0c-459b-8cad-ab36e9a08d69@redhat.com> (raw)
In-Reply-To: <257d6562-51fb-867a-e65c-13418c6ce888@loongson.cn>

Hello,

On 11/17/23 02:14, maobibo wrote:
> Thomas,
> 
> Linux 6.7-rc1 has already released, LoongArch KVM is supported in this version. LoongArch qemu KVM function depends on linux-headers and I do not know whether LoongArch qemu KVM can be merged in 8.2 cycle.

It's too late for 8.2. See https://wiki.qemu.org/Planning/8.2.

Thanks,

C.



> Regards
> Bibo Mao
> 
> 
> On 2023/11/16 下午9:19, Thomas Huth wrote:
>> On 15/11/2023 11.07, gaosong wrote:
>>> Hi,
>>>
>>> Can this patch be merged in during the 8.2 cycle?
>>
>>   Hi!
>>
>> We normally do linux-headers updates along with the patches that need the new definitions ... so is there an urgent reason to push this stand-alone
>> patch into 8.2 without any patches that require these new definitions?
>>
>>   Thomas
> 
> 



  reply	other threads:[~2023-11-17  6:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  1:54 [PATCH] linux-headers: Synchronize linux headers from linux v6.7.0-rc1 Tianrui Zhao
2023-11-15 10:07 ` gaosong
2023-11-16 13:19   ` Thomas Huth
2023-11-17  1:14     ` maobibo
2023-11-17  6:35       ` Cédric Le Goater [this message]
2023-11-17  6:45         ` maobibo
2023-11-17  6:44       ` Thomas Huth

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=800a75b9-8c0c-459b-8cad-ab36e9a08d69@redhat.com \
    --to=clg@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=gaosong@loongson.cn \
    --cc=lixianglai@loongson.cn \
    --cc=maobibo@loongson.cn \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    --cc=zhaotianrui@loongson.cn \
    /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).