From: akpm@linux-foundation.org
To: andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
linux@roeck-us.net, mm-commits@vger.kernel.org,
yury.norov@gmail.com
Subject: [folded-merged] lib-add-test-for-bitmap_parse-fix-2.patch removed from -mm tree
Date: Mon, 03 Feb 2020 17:13:27 -0800 [thread overview]
Message-ID: <20200204011327.ydd7G8Pcu%akpm@linux-foundation.org> (raw)
The patch titled
Subject: lib/test_bitmap: fix address space when test user buffer
has been removed from the -mm tree. Its filename was
lib-add-test-for-bitmap_parse-fix-2.patch
This patch was dropped because it was folded into lib-add-test-for-bitmap_parse.patch
------------------------------------------------------
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: lib/test_bitmap: fix address space when test user buffer
Force address space to avoid the following warning:
lib/test_bitmap.c:461:53: warning: incorrect type in argument 1 (different address spaces)
lib/test_bitmap.c:461:53: expected char const [noderef] <asn:1> *ubuf
lib/test_bitmap.c:461:53: got char const *in
Link: http://lkml.kernel.org/r/20200109103601.45929-2-andriy.shevchenko@linux.intel.com
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Yury Norov <yury.norov@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/test_bitmap.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/lib/test_bitmap.c~lib-add-test-for-bitmap_parse-fix-2
+++ a/lib/test_bitmap.c
@@ -450,7 +450,8 @@ static void __init __test_bitmap_parse(i
set_fs(KERNEL_DS);
time = ktime_get();
- err = bitmap_parse_user(test.in, len, bmap, test.nbits);
+ err = bitmap_parse_user((__force const char __user *)test.in, len,
+ bmap, test.nbits);
time = ktime_get() - time;
set_fs(orig_fs);
} else {
_
Patches currently in -mm which might be from andriy.shevchenko@linux.intel.com are
lib-add-test-for-bitmap_parse.patch
reply other threads:[~2020-02-04 1:13 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=20200204011327.ydd7G8Pcu%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=mm-commits@vger.kernel.org \
--cc=yury.norov@gmail.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;
as well as URLs for NNTP newsgroup(s).