public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Yury Norov <yury.norov@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] lib/test_bitmap: Fix address space when test user buffer
Date: Thu, 9 Jan 2020 15:00:19 -0800	[thread overview]
Message-ID: <20200109230019.GA5938@roeck-us.net> (raw)
In-Reply-To: <20200109135253.ab86a6a61899221e1e4609fa@linux-foundation.org>

On Thu, Jan 09, 2020 at 01:52:53PM -0800, Andrew Morton wrote:
> On Thu, 9 Jan 2020 23:04:59 +0200 Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> 
> > On Thu, Jan 9, 2020 at 10:53 PM Andrew Morton <akpm@linux-foundation.org> wrote:
> > >
> > > On Thu,  9 Jan 2020 12:36:01 +0200 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > > 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
> > >
> > > We did this in
> > >
> > > commit 17b6753ff08bc47f50da09f5185849172c598315
> > > Author:     Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > AuthorDate: Wed Dec 4 16:53:06 2019 -0800
> > > Commit:     Linus Torvalds <torvalds@linux-foundation.org>
> > > CommitDate: Wed Dec 4 19:44:14 2019 -0800
> > >
> > >     lib/test_bitmap: force argument of bitmap_parselist_user() to proper address space
> > 
> > This is for "parseLIST", while new patch for "parse".
> 
> Oh.  This is a fix against the mm patch
> lib-add-test-for-bitmap_parse.patch.  Please tell us such things!
> 
> But [patch 1/2] is applicable to current mainline, yes?
> 
Yes

Guenter

      reply	other threads:[~2020-01-09 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 10:36 [PATCH v2 1/2] lib/test_bitmap: Correct test data offsets for 32-bit Andy Shevchenko
2020-01-09 10:36 ` [PATCH v2 2/2] lib/test_bitmap: Fix address space when test user buffer Andy Shevchenko
2020-01-09 20:08   ` Andrew Morton
2020-01-09 21:04     ` Andy Shevchenko
2020-01-09 21:52       ` Andrew Morton
2020-01-09 23:00         ` Guenter Roeck [this message]

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=20200109230019.GA5938@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --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