From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Huacai Chen <chenhuacai@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Christoph Hellwig <hch@lst.de>,
Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.de>,
John Garry <john.g.garry@oracle.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Remove the BOUNCE config option
Date: Wed, 15 Oct 2025 09:12:34 +0530 [thread overview]
Message-ID: <934d3de7-0f46-494a-831f-d04209ea4a8f@arm.com> (raw)
In-Reply-To: <20251013095620.1111061-1-chenhuacai@loongson.cn>
On 13/10/25 3:26 PM, Huacai Chen wrote:
> Commit eeadd68e2a5f6bfe0bf10 ("block: remove bounce buffering support")
> remove block/bounce.c but left the BOUNCE config option. Now this option
> has no users, so remove it.
>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> ---
> mm/Kconfig | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/mm/Kconfig b/mm/Kconfig
> index 0e26f4fc8717..e47321051d76 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -695,15 +695,6 @@ config PCP_BATCH_SCALE_MAX
> config PHYS_ADDR_T_64BIT
> def_bool 64BIT
>
> -config BOUNCE
> - bool "Enable bounce buffers"
> - default y
> - depends on BLOCK && MMU && HIGHMEM
> - help
> - Enable bounce buffers for devices that cannot access the full range of
> - memory available to the CPU. Enabled by default when HIGHMEM is
> - selected, but you may say n to override this.
> -
> config MMU_NOTIFIER
> bool
> select INTERVAL_TREE
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
prev parent reply other threads:[~2025-10-15 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 9:56 Huacai Chen
2025-10-13 12:52 ` David Hildenbrand
2025-10-14 4:18 ` Christoph Hellwig
2025-10-14 13:07 ` Jens Axboe
2025-10-15 3:42 ` Anshuman Khandual [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=934d3de7-0f46-494a-831f-d04209ea4a8f@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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