From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, handai.szj@taobao.com, dylany@fb.com,
axboe@kernel.dk, zhangqilong3@huawei.com,
akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] eventfd-change-int-to-__u64-in-eventfd_signal-ifndef-config_eventfd.patch removed from -mm tree
Date: Sun, 11 Dec 2022 19:31:08 -0800 [thread overview]
Message-ID: <20221212033109.6CB0BC433D2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: eventfd: change int to __u64 in eventfd_signal() ifndef CONFIG_EVENTFD
has been removed from the -mm tree. Its filename was
eventfd-change-int-to-__u64-in-eventfd_signal-ifndef-config_eventfd.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Zhang Qilong <zhangqilong3@huawei.com>
Subject: eventfd: change int to __u64 in eventfd_signal() ifndef CONFIG_EVENTFD
Date: Thu, 24 Nov 2022 22:01:54 +0800
Commit ee62c6b2dc93 ("eventfd: change int to __u64 in eventfd_signal()")
forgot to change int to __u64 in the CONFIG_EVENTFD=n stub function.
Link: https://lkml.kernel.org/r/20221124140154.104680-1-zhangqilong3@huawei.com
Fixes: ee62c6b2dc93 ("eventfd: change int to __u64 in eventfd_signal()")
Signed-off-by: Zhang Qilong <zhangqilong3@huawei.com>
Cc: Dylan Yudaken <dylany@fb.com>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Sha Zhengju <handai.szj@taobao.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/eventfd.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/include/linux/eventfd.h~eventfd-change-int-to-__u64-in-eventfd_signal-ifndef-config_eventfd
+++ a/include/linux/eventfd.h
@@ -61,7 +61,7 @@ static inline struct eventfd_ctx *eventf
return ERR_PTR(-ENOSYS);
}
-static inline int eventfd_signal(struct eventfd_ctx *ctx, int n)
+static inline int eventfd_signal(struct eventfd_ctx *ctx, __u64 n)
{
return -ENOSYS;
}
_
Patches currently in -mm which might be from zhangqilong3@huawei.com are
reply other threads:[~2022-12-12 3:31 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=20221212033109.6CB0BC433D2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dylany@fb.com \
--cc=handai.szj@taobao.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=zhangqilong3@huawei.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.