linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pintu Kumar <quic_pintu@quicinc.com>
To: <linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>,
	<linux-mm@kvack.org>, <hch@lst.de>, <m.szyprowski@samsung.com>,
	<robin.murphy@arm.com>, <iommu@lists.linux.dev>
Cc: <quic_pintu@quicinc.com>, <pintu.ping@gmail.com>
Subject: [PATCH v2] dma-contiguous: define proper name for global cma region
Date: Sat, 29 Jul 2023 08:05:15 +0530	[thread overview]
Message-ID: <1690598115-26287-1-git-send-email-quic_pintu@quicinc.com> (raw)
In-Reply-To: <1690567693-22082-1-git-send-email-quic_pintu@quicinc.com>

The current global cma region name defined as "reserved"
which is misleading, creates confusion and too generic.

Also, the default cma allocation happens from global cma region,
so, if one has to figure out all allocations happening from
global cma region, this seems easier.

Thus, change the name from "reserved" to "global-cma-region".

Signed-off-by: Pintu Kumar <quic_pintu@quicinc.com>
---
 kernel/dma/contiguous.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/dma/contiguous.c b/kernel/dma/contiguous.c
index 26a8e53..4628b62 100644
--- a/kernel/dma/contiguous.c
+++ b/kernel/dma/contiguous.c
@@ -237,7 +237,7 @@ int __init dma_contiguous_reserve_area(phys_addr_t size, phys_addr_t base,
 	int ret;
 
 	ret = cma_declare_contiguous(base, size, limit, 0, 0, fixed,
-					"reserved", res_cma);
+					"global-cma-region", res_cma);
 	if (ret)
 		return ret;
 
-- 
2.7.4



  reply	other threads:[~2023-07-29  2:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 18:08 [PATCH] " Pintu Kumar
2023-07-29  2:35 ` Pintu Kumar [this message]
2023-07-31 11:21   ` [PATCH v2] " Christoph Hellwig
2023-08-01 17:12     ` Pintu Agarwal
2023-08-01 17:18       ` Christoph Hellwig
2023-08-02  5:39         ` John Stultz
2023-08-02  9:47           ` Christoph Hellwig
2023-08-03 17:34             ` Pintu Agarwal
2023-08-09 15:04               ` Pintu Agarwal
2023-08-10  0:57                 ` John Stultz

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=1690598115-26287-1-git-send-email-quic_pintu@quicinc.com \
    --to=quic_pintu@quicinc.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=pintu.ping@gmail.com \
    --cc=robin.murphy@arm.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