From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Pablo Neira Ayuso <pablo@netfilter.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] lib: Fix bitmap_cut() for overlaps, add test
Date: Mon, 8 Jun 2020 13:13:02 +0300 [thread overview]
Message-ID: <20200608101302.GF2428291@smile.fi.intel.com> (raw)
In-Reply-To: <cover.1591606281.git.sbrivio@redhat.com>
On Mon, Jun 08, 2020 at 11:13:27AM +0200, Stefano Brivio wrote:
> Patch 1/2 addresses the issue Yury reported with partially overlapping
> src and dst in bitmap_cut(), and 2/2 adds a test that covers basic
> functionality as well as this case.
>
>
FWIW, after addressing comments per test case,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Stefano Brivio (2):
> lib: Fix bitmap_cut() for partial overlapping case
> lib: Add test for bitmap_cut()
>
> lib/bitmap.c | 4 ++--
> lib/test_bitmap.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 62 insertions(+), 2 deletions(-)
>
> --
> 2.26.2
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-06-08 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 9:13 [PATCH 0/2] lib: Fix bitmap_cut() for overlaps, add test Stefano Brivio
2020-06-08 9:13 ` [PATCH 1/2] lib: Fix bitmap_cut() for partial overlapping case Stefano Brivio
2020-06-08 9:13 ` [PATCH 2/2] lib: Add test for bitmap_cut() Stefano Brivio
2020-06-08 10:12 ` Andy Shevchenko
2020-06-08 10:27 ` Stefano Brivio
2020-06-08 11:31 ` Andy Shevchenko
2020-06-08 11:51 ` Stefano Brivio
2020-06-10 7:42 ` [lib] 0a1d3d4a3c: Kernel_panic-not_syncing:stack-protector:Kernel_stack_is_corrupted_in:test_bitmap_init kernel test robot
2020-06-08 10:13 ` Andy Shevchenko [this message]
2020-06-14 17:40 [PATCH 0/2] lib: Fix bitmap_cut() for overlaps, add test Stefano Brivio
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=20200608101302.GF2428291@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pablo@netfilter.org \
--cc=sbrivio@redhat.com \
--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).