All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zhai He <zhai.he@nxp.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"sboyd@kernel.org" <sboyd@kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Zhipeng Wang <zhipeng.wang_1@nxp.com>,
	Jindong Yue <jindong.yue@nxp.com>
Subject: Re: [EXT] Re: [PATCH] Supports to use the default CMA when the device-specified CMA memory is not enough.
Date: Wed, 12 Jun 2024 09:47:46 +0200	[thread overview]
Message-ID: <2024061215-strum-quarry-c574@gregkh> (raw)
In-Reply-To: <AS1PR04MB955995BF689849177D95DE28EAC02@AS1PR04MB9559.eurprd04.prod.outlook.com>

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Wed, Jun 12, 2024 at 07:34:56AM +0000, Zhai He wrote:
> Thanks Greg for your review.
> The reason I changed the error level is because these logs will be printed
> when memory allocation from the specified device CMA fails, but if the
> allocation fails, it will be allocated from the default cma area. It can
> easily mislead developers' judgment, so I changed it to debug level.

Then you need to explain this in the changelog text :(

thanks,

greg k-h

      reply	other threads:[~2024-06-12  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  2:38 [PATCH] Supports to use the default CMA when the device-specified CMA memory is not enough zhai.he
2024-06-12  2:39 ` kernel test robot
2024-06-12  7:20 ` Greg KH
2024-06-12  7:34   ` [EXT] " Zhai He
2024-06-12  7:47     ` Greg KH [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=2024061215-strum-quarry-c574@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jindong.yue@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sboyd@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zhai.he@nxp.com \
    --cc=zhipeng.wang_1@nxp.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.