From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,andriy.shevchenko@linux.intel.com,aardelean@baylibre.com,mingo@kernel.org,akpm@linux-foundation.org
Subject: + kernelh-move-read-write-definitions-to-linux-typesh.patch added to mm-nonmm-unstable branch
Date: Sun, 06 Apr 2025 21:53:51 -0700 [thread overview]
Message-ID: <20250407045351.DA4EEC4CEDD@smtp.kernel.org> (raw)
The patch titled
Subject: kernel.h: move READ/WRITE definitions to <linux/types.h>
has been added to the -mm mm-nonmm-unstable branch. Its filename is
kernelh-move-read-write-definitions-to-linux-typesh.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/kernelh-move-read-write-definitions-to-linux-typesh.patch
This patch will later appear in the mm-nonmm-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days
------------------------------------------------------
From: Ingo Molnar <mingo@kernel.org>
Subject: kernel.h: move READ/WRITE definitions to <linux/types.h>
Date: Mon, 24 Mar 2025 12:50:24 +0200
Patch series "kernel.h: Move out a couple of macros and constants".
kernel.h hosts a couple of macros and constants that may be better placed.
Do that. Also add missing documentation. No functional changes
intended.
This patch (of 2):
Headers shouldn't be forced to include <linux/kernel.h> just to
gain these simple constants.
Link: https://lkml.kernel.org/r/20250324105228.775784-1-andriy.shevchenko@linux.intel.com
Link: https://lkml.kernel.org/r/20250324105228.775784-2-andriy.shevchenko@linux.intel.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Alexandru Ardelean <aardelean@baylibre.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/kernel.h | 4 ----
include/linux/types.h | 4 ++++
2 files changed, 4 insertions(+), 4 deletions(-)
--- a/include/linux/kernel.h~kernelh-move-read-write-definitions-to-linux-typesh
+++ a/include/linux/kernel.h
@@ -41,10 +41,6 @@
#define STACK_MAGIC 0xdeadbeef
-/* generic data direction definitions */
-#define READ 0
-#define WRITE 1
-
#define PTR_IF(cond, ptr) ((cond) ? (ptr) : NULL)
#define u64_to_user_ptr(x) ( \
--- a/include/linux/types.h~kernelh-move-read-write-definitions-to-linux-typesh
+++ a/include/linux/types.h
@@ -136,6 +136,10 @@ typedef s64 ktime_t;
typedef u64 sector_t;
typedef u64 blkcnt_t;
+/* generic data direction definitions */
+#define READ 0
+#define WRITE 1
+
/*
* The type of an index into the pagecache.
*/
_
Patches currently in -mm which might be from mingo@kernel.org are
kernelh-move-read-write-definitions-to-linux-typesh.patch
reply other threads:[~2025-04-07 4:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250407045351.DA4EEC4CEDD@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=aardelean@baylibre.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=mingo@kernel.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 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.