From: akpm@linux-foundation.org
To: acme@redhat.com, amritha.nambiar@intel.com,
andriy.shevchenko@linux.intel.com, chris@chris-wilson.co.uk,
keescook@chromium.org, linux@rasmusvillemoes.dk,
mm-commits@vger.kernel.org, mszeredi@redhat.com,
steffen.klassert@secunet.com, tobin@kernel.org,
vineet.gupta1@synopsys.com, will.deacon@arm.com,
willemb@google.com, willy@infradead.org, yury.norov@gmail.com
Subject: [folded-merged] lib-add-test-for-bitmap_parse-fix.patch removed from -mm tree
Date: Mon, 03 Feb 2020 17:13:23 -0800 [thread overview]
Message-ID: <20200204011323.xPHmRNNaV%akpm@linux-foundation.org> (raw)
The patch titled
Subject: fix rebase issue
has been removed from the -mm tree. Its filename was
lib-add-test-for-bitmap_parse-fix.patch
This patch was dropped because it was folded into lib-add-test-for-bitmap_parse.patch
------------------------------------------------------
From: Yury Norov <yury.norov@gmail.com>
Subject: fix rebase issue
Link: http://lkml.kernel.org/r/20200102182659.6685-1-yury.norov@gmail.com
Signed-off-by: Yury Norov <yury.norov@gmail.com>
Cc: Amritha Nambiar <amritha.nambiar@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Kees Cook <keescook@chromium.org>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Miklos Szeredi <mszeredi@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Steffen Klassert <steffen.klassert@secunet.com>
Cc: "Tobin C . Harding" <tobin@kernel.org>
Cc: Vineet Gupta <vineet.gupta1@synopsys.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: Willem de Bruijn <willemb@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/test_bitmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/lib/test_bitmap.c~lib-add-test-for-bitmap_parse-fix
+++ a/lib/test_bitmap.c
@@ -350,7 +350,6 @@ static const struct test_bitmap_parselis
{-EINVAL, "0-31:a/1", NULL, 8, 0},
{-EINVAL, "0-\n", NULL, 8, 0},
-#undef step
};
static void __init __test_bitmap_parselist(int is_user)
@@ -431,6 +430,7 @@ static const struct test_bitmap_parselis
{-EOVERFLOW, "badf00d,deadbeef,1,0", NULL, 90, 0},
{-EOVERFLOW, "fbadf00d,deadbeef,1,0", NULL, 95, 0},
{-EOVERFLOW, "badf00d,deadbeef,1,0", NULL, 100, 0},
+#undef step
};
static void __init __test_bitmap_parse(int is_user)
_
Patches currently in -mm which might be from yury.norov@gmail.com are
lib-string-add-strnchrnul.patch
bitops-more-bits_to_-macros.patch
lib-add-test-for-bitmap_parse.patch
lib-make-bitmap_parse_user-a-wrapper-on-bitmap_parse.patch
lib-rework-bitmap_parse.patch
lib-new-testcases-for-bitmap_parse_user.patch
cpumask-dont-calculate-length-of-the-input-string.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=20200204011323.xPHmRNNaV%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=acme@redhat.com \
--cc=amritha.nambiar@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mm-commits@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=tobin@kernel.org \
--cc=vineet.gupta1@synopsys.com \
--cc=will.deacon@arm.com \
--cc=willemb@google.com \
--cc=willy@infradead.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).