linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: 高翔 <gaoxiang17@xiaomi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"david@redhat.com" <david@redhat.com>
Subject: 答复: 答复: [External Mail]+ mm-cma-print-total-and-used-count-in-cma_alloc.patch added to mm-unstable branch
Date: Fri, 27 Sep 2024 00:46:44 +0000	[thread overview]
Message-ID: <cb640f960feb43bc8cc280474314e52f@xiaomi.com> (raw)
In-Reply-To: <20240926171747.bacbd2b5d62d4a34926f0d4f@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

If you pass the regular integration testing, it will be classified as 6.13 material, and then finally merge into version 6.13?

________________________________
发件人: Andrew Morton <akpm@linux-foundation.org>
发送时间: 2024年9月27日 8:17:47
收件人: 高翔
抄送: mm-commits@vger.kernel.org; linux-mm@kvack.org; linux-kernel@vger.kernel.org; david@redhat.com
主题: Re: 答复: [External Mail]+ mm-cma-print-total-and-used-count-in-cma_alloc.patch added to mm-unstable branch

[外部邮件] 此邮件来源于小米公司外部,请谨慎处理。若对邮件安全性存疑,请将邮件转发给misec@xiaomi.com进行反馈

On Thu, 26 Sep 2024 23:19:25 +0000 高翔 <gaoxiang17@xiaomi.com> wrote:

> So now we're ready to merge into master?
>

Nope.  There's a review question I'd like answered and the patch should
go through our regular integration testing.  This is 6.13 material.

[-- Attachment #2: Type: text/html, Size: 2366 bytes --]

  reply	other threads:[~2024-09-27  0:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240926202540.E47E3C4CEC7@smtp.kernel.org>
2024-09-26 23:19 ` 高翔
2024-09-27  0:17   ` Andrew Morton
2024-09-27  0:46     ` 高翔 [this message]
2024-09-27 12:16       ` 答复: " David Hildenbrand

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=cb640f960feb43bc8cc280474314e52f@xiaomi.com \
    --to=gaoxiang17@xiaomi.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    /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