From: Eliav Farber <farbere@amazon.com>
To: <gregkh@linuxfoundation.org>, <stable@vger.kernel.org>,
<linux@armlinux.org.uk>, <jdike@addtoit.com>, <richard@nod.at>,
<anton.ivanov@cambridgegreys.com>, <dave.hansen@linux.intel.com>,
<luto@kernel.org>, <peterz@infradead.org>, <tglx@linutronix.de>,
<mingo@redhat.com>, <bp@alien8.de>, <x86@kernel.org>,
<hpa@zytor.com>, <tony.luck@intel.com>, <qiuxu.zhuo@intel.com>,
<mchehab@kernel.org>, <james.morse@arm.com>, <rric@kernel.org>,
<harry.wentland@amd.com>, <sunpeng.li@amd.com>,
<alexander.deucher@amd.com>, <christian.koenig@amd.com>,
<airlied@linux.ie>, <daniel@ffwll.ch>, <evan.quan@amd.com>,
<james.qian.wang@arm.com>, <liviu.dudau@arm.com>,
<mihail.atanassov@arm.com>, <brian.starkey@arm.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <robdclark@gmail.com>, <sean@poorly.run>,
<jdelvare@suse.com>, <linux@roeck-us.net>, <fery@cypress.com>,
<dmitry.torokhov@gmail.com>, <agk@redhat.com>,
<snitzer@redhat.com>, <dm-devel@redhat.com>, <rajur@chelsio.com>,
<davem@davemloft.net>, <kuba@kernel.org>,
<peppe.cavallaro@st.com>, <alexandre.torgue@st.com>,
<joabreu@synopsys.com>, <mcoquelin.stm32@gmail.com>,
<malattia@linux.it>, <hdegoede@redhat.com>,
<mgross@linux.intel.com>, <intel-linux-scu@intel.com>,
<artur.paszkiewicz@intel.com>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <sakari.ailus@linux.intel.com>,
<clm@fb.com>, <josef@toxicpanda.com>, <dsterba@suse.com>,
<xiang@kernel.org>, <chao@kernel.org>, <jack@suse.com>,
<tytso@mit.edu>, <adilger.kernel@dilger.ca>, <dushistov@mail.ru>,
<luc.vanoostenryck@gmail.com>, <rostedt@goodmis.org>,
<pmladek@suse.com>, <sergey.senozhatsky@gmail.com>,
<andriy.shevchenko@linux.intel.com>, <linux@rasmusvillemoes.dk>,
<minchan@kernel.org>, <ngupta@vflare.org>,
<akpm@linux-foundation.org>, <kuznet@ms2.inr.ac.ru>,
<yoshfuji@linux-ipv6.org>, <pablo@netfilter.org>,
<kadlec@netfilter.org>, <fw@strlen.de>, <jmaloy@redhat.com>,
<ying.xue@windriver.com>, <willy@infradead.org>,
<farbere@amazon.com>, <sashal@kernel.org>,
<ruanjinjie@huawei.com>, <David.Laight@ACULAB.COM>,
<herve.codina@bootlin.com>, <Jason@zx2c4.com>,
<keescook@chromium.org>, <kbusch@kernel.org>, <nathan@kernel.org>,
<bvanassche@acm.org>, <ndesaulniers@google.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-um@lists.infradead.org>,
<linux-edac@vger.kernel.org>, <amd-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<linux-arm-msm@vger.kernel.org>,
<freedreno@lists.freedesktop.org>, <linux-hwmon@vger.kernel.org>,
<linux-input@vger.kernel.org>, <linux-media@vger.kernel.org>,
<netdev@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<platform-driver-x86@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, <linux-staging@lists.linux.dev>,
<linux-btrfs@vger.kernel.org>, <linux-erofs@lists.ozlabs.org>,
<linux-ext4@vger.kernel.org>, <linux-sparse@vger.kernel.org>,
<linux-mm@kvack.org>, <netfilter-devel@vger.kernel.org>,
<coreteam@netfilter.org>, <tipc-discussion@lists.sourceforge.net>
Cc: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH v2 02/27 5.10.y] btrfs: remove duplicated in_range() macro
Date: Fri, 17 Oct 2025 09:04:54 +0000 [thread overview]
Message-ID: <20251017090519.46992-3-farbere@amazon.com> (raw)
In-Reply-To: <20251017090519.46992-1-farbere@amazon.com>
From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
[ Upstream commit cea628008fc8c6c9c7b53902f6659e040f33c790 ]
The in_range() macro is defined twice in btrfs' source, once in ctree.h
and once in misc.h.
Remove the definition in ctree.h and include misc.h in the files depending
on it.
Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Signed-off-by: Eliav Farber <farbere@amazon.com>
---
fs/btrfs/ctree.h | 2 --
fs/btrfs/extent_io.c | 1 +
fs/btrfs/file-item.c | 1 +
fs/btrfs/raid56.c | 1 +
4 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index d9d6a57acafe..a9926fb10c49 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -3597,8 +3597,6 @@ static inline int btrfs_defrag_cancelled(struct btrfs_fs_info *fs_info)
return signal_pending(current);
}
-#define in_range(b, first, len) ((b) >= (first) && (b) < (first) + (len))
-
/* Sanity test specific functions */
#ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS
void btrfs_test_destroy_inode(struct inode *inode);
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index 8498994ef5c6..489d370ddd60 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -13,6 +13,7 @@
#include <linux/pagevec.h>
#include <linux/prefetch.h>
#include <linux/cleancache.h>
+#include "misc.h"
#include "extent_io.h"
#include "extent-io-tree.h"
#include "extent_map.h"
diff --git a/fs/btrfs/file-item.c b/fs/btrfs/file-item.c
index cbea4f572155..6e46da3ee433 100644
--- a/fs/btrfs/file-item.c
+++ b/fs/btrfs/file-item.c
@@ -9,6 +9,7 @@
#include <linux/highmem.h>
#include <linux/sched/mm.h>
#include <crypto/hash.h>
+#include "misc.h"
#include "ctree.h"
#include "disk-io.h"
#include "transaction.h"
diff --git a/fs/btrfs/raid56.c b/fs/btrfs/raid56.c
index 9678d7fa4dcc..ed3e40a4a3cb 100644
--- a/fs/btrfs/raid56.c
+++ b/fs/btrfs/raid56.c
@@ -13,6 +13,7 @@
#include <linux/list_sort.h>
#include <linux/raid/xor.h>
#include <linux/mm.h>
+#include "misc.h"
#include "ctree.h"
#include "disk-io.h"
#include "volumes.h"
--
2.47.3
next prev parent reply other threads:[~2025-10-17 9:06 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 9:04 [PATCH v2 00/27 5.10.y] Backport minmax.h updates from v6.17-rc7 Eliav Farber
2025-10-17 9:04 ` [PATCH v2 01/27 5.10.y] overflow, tracing: Define the is_signed_type() macro once Eliav Farber
2025-10-17 11:59 ` Greg KH
2025-10-17 12:16 ` Farber, Eliav
2025-10-17 13:21 ` Greg KH
2025-10-17 13:48 ` Patch "overflow, tracing: Define the is_signed_type() macro once" has been added to the 5.10-stable tree gregkh
2025-10-17 9:04 ` Eliav Farber [this message]
2025-10-17 13:48 ` Patch "btrfs: remove duplicated in_range() macro" " gregkh
2025-10-17 9:04 ` [PATCH v2 03/27 5.10.y] minmax: sanity check constant bounds when clamping Eliav Farber
2025-10-17 13:48 ` Patch "minmax: sanity check constant bounds when clamping" has been added to the 5.10-stable tree gregkh
2025-10-17 9:04 ` [PATCH v2 04/27 5.10.y] minmax: clamp more efficiently by avoiding extra comparison Eliav Farber
2025-10-17 13:48 ` Patch "minmax: clamp more efficiently by avoiding extra comparison" has been added to the 5.10-stable tree gregkh
2025-10-17 9:04 ` [PATCH v2 05/27 5.10.y] minmax: add in_range() macro Eliav Farber
2025-10-17 13:48 ` Patch "minmax: add in_range() macro" has been added to the 5.10-stable tree gregkh
2025-10-17 9:04 ` [PATCH v2 06/27 5.10.y] minmax: Introduce {min,max}_array() Eliav Farber
2025-10-17 13:48 ` Patch "minmax: Introduce {min,max}_array()" has been added to the 5.10-stable tree gregkh
2025-10-17 9:04 ` [PATCH v2 07/27 5.10.y] minmax: deduplicate __unconst_integer_typeof() Eliav Farber
2025-10-17 13:48 ` Patch "minmax: deduplicate __unconst_integer_typeof()" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 08/27 5.10.y] minmax: fix header inclusions Eliav Farber
2025-10-17 13:48 ` Patch "minmax: fix header inclusions" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 09/27 5.10.y] minmax: allow min()/max()/clamp() if the arguments have the same signedness Eliav Farber
2025-10-17 13:48 ` Patch "minmax: allow min()/max()/clamp() if the arguments have the same signedness." has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 10/27 5.10.y] minmax: fix indentation of __cmp_once() and __clamp_once() Eliav Farber
2025-10-17 13:48 ` Patch "minmax: fix indentation of __cmp_once() and __clamp_once()" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 11/27 5.10.y] minmax: allow comparisons of 'int' against 'unsigned char/short' Eliav Farber
2025-10-17 13:48 ` Patch "minmax: allow comparisons of 'int' against 'unsigned char/short'" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 12/27 5.10.y] minmax: relax check to allow comparison between unsigned arguments and signed constants Eliav Farber
2025-10-17 13:48 ` Patch "minmax: relax check to allow comparison between unsigned arguments and signed constants" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 13/27 5.10.y] minmax: avoid overly complicated constant expressions in VM code Eliav Farber
2025-10-17 13:48 ` Patch "minmax: avoid overly complicated constant expressions in VM code" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 14/27 5.10.y] minmax: add a few more MIN_T/MAX_T users Eliav Farber
2025-10-17 13:48 ` Patch "minmax: add a few more MIN_T/MAX_T users" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 15/27 5.10.y] minmax: simplify and clarify min_t()/max_t() implementation Eliav Farber
2025-10-17 13:48 ` Patch "minmax: simplify and clarify min_t()/max_t() implementation" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 16/27 5.10.y] minmax: make generic MIN() and MAX() macros available everywhere Eliav Farber
2025-10-17 13:48 ` Patch "minmax: make generic MIN() and MAX() macros available everywhere" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 17/27 5.10.y] minmax: don't use max() in situations that want a C constant expression Eliav Farber
2025-10-17 13:48 ` Patch "minmax: don't use max() in situations that want a C constant expression" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 18/27 5.10.y] minmax: simplify min()/max()/clamp() implementation Eliav Farber
2025-10-17 13:48 ` Patch "minmax: simplify min()/max()/clamp() implementation" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 19/27 5.10.y] minmax: improve macro expansion and type checking Eliav Farber
2025-10-17 13:48 ` Patch "minmax: improve macro expansion and type checking" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 20/27 5.10.y] minmax: fix up min3() and max3() too Eliav Farber
2025-10-17 13:48 ` Patch "minmax: fix up min3() and max3() too" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 21/27 5.10.y] minmax.h: add whitespace around operators and after commas Eliav Farber
2025-10-17 13:48 ` Patch "minmax.h: add whitespace around operators and after commas" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 22/27 5.10.y] minmax.h: update some comments Eliav Farber
2025-10-17 13:48 ` Patch "minmax.h: update some comments" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 23/27 5.10.y] minmax.h: reduce the #define expansion of min(), max() and clamp() Eliav Farber
2025-10-17 13:48 ` Patch "minmax.h: reduce the #define expansion of min(), max() and clamp()" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 24/27 5.10.y] minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp() Eliav Farber
2025-10-17 13:48 ` Patch "minmax.h: use BUILD_BUG_ON_MSG() for the lo < hi test in clamp()" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 25/27 5.10.y] minmax.h: move all the clamp() definitions after the min/max() ones Eliav Farber
2025-10-17 13:48 ` Patch "minmax.h: move all the clamp() definitions after the min/max() ones" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 26/27 5.10.y] minmax.h: simplify the variants of clamp() Eliav Farber
2025-10-17 13:48 ` Patch "minmax.h: simplify the variants of clamp()" has been added to the 5.10-stable tree gregkh
2025-10-17 9:05 ` [PATCH v2 27/27 5.10.y] minmax.h: remove some #defines that are only expanded once Eliav Farber
2025-10-17 13:48 ` Patch "minmax.h: remove some #defines that are only expanded once" has been added to the 5.10-stable tree gregkh
2025-10-17 15:03 ` [PATCH v2 00/27 5.10.y] Backport minmax.h updates from v6.17-rc7 Greg KH
2025-10-17 16:09 ` Nathan Chancellor
2025-10-19 12:38 ` Greg KH
2025-10-18 20:07 ` Farber, Eliav
2025-10-19 12:37 ` Greg KH
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=20251017090519.46992-3-farbere@amazon.com \
--to=farbere@amazon.com \
--cc=David.Laight@ACULAB.COM \
--cc=Jason@zx2c4.com \
--cc=adilger.kernel@dilger.ca \
--cc=agk@redhat.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=alexandre.torgue@st.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=artur.paszkiewicz@intel.com \
--cc=bp@alien8.de \
--cc=brian.starkey@arm.com \
--cc=bvanassche@acm.org \
--cc=chao@kernel.org \
--cc=christian.koenig@amd.com \
--cc=clm@fb.com \
--cc=coreteam@netfilter.org \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dsterba@suse.com \
--cc=dushistov@mail.ru \
--cc=evan.quan@amd.com \
--cc=fery@cypress.com \
--cc=freedreno@lists.freedesktop.org \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=harry.wentland@amd.com \
--cc=hdegoede@redhat.com \
--cc=herve.codina@bootlin.com \
--cc=hpa@zytor.com \
--cc=intel-linux-scu@intel.com \
--cc=jack@suse.com \
--cc=james.morse@arm.com \
--cc=james.qian.wang@arm.com \
--cc=jdelvare@suse.com \
--cc=jdike@addtoit.com \
--cc=jejb@linux.ibm.com \
--cc=jmaloy@redhat.com \
--cc=joabreu@synopsys.com \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=kadlec@netfilter.org \
--cc=kbusch@kernel.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-um@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=liviu.dudau@arm.com \
--cc=luc.vanoostenryck@gmail.com \
--cc=luto@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=malattia@linux.it \
--cc=martin.petersen@oracle.com \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mgross@linux.intel.com \
--cc=mihail.atanassov@arm.com \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ngupta@vflare.org \
--cc=pablo@netfilter.org \
--cc=peppe.cavallaro@st.com \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=qiuxu.zhuo@intel.com \
--cc=rajur@chelsio.com \
--cc=richard@nod.at \
--cc=robdclark@gmail.com \
--cc=rostedt@goodmis.org \
--cc=rric@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sashal@kernel.org \
--cc=sean@poorly.run \
--cc=sergey.senozhatsky@gmail.com \
--cc=snitzer@redhat.com \
--cc=stable@vger.kernel.org \
--cc=sunpeng.li@amd.com \
--cc=tglx@linutronix.de \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tony.luck@intel.com \
--cc=tytso@mit.edu \
--cc=tzimmermann@suse.de \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=xiang@kernel.org \
--cc=ying.xue@windriver.com \
--cc=yoshfuji@linux-ipv6.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