linux-um archives
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Richard Weinberger <richard@nod.at>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	uml-devel <user-mode-linux-devel@lists.sourceforge.net>,
	Stephen Bates <sbates@raithlin.com>,
	Jeff Dike <jdike@addtoit.com>, Al Viro <viro@zeniv.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] um: add dummy ioremap and iounmap functions
Date: Thu, 8 Jun 2017 12:53:40 -0600	[thread overview]
Message-ID: <348baf8d-b42f-13a7-3398-cb0268d7c693@deltatee.com> (raw)
In-Reply-To: <8ad31524-dfc3-4fc4-f725-a8899aea9234@deltatee.com>

Any thoughts on this? My patches for the other architectures are already
in linux-next. um is the only one that remains.

Thanks,

Logan

On 27/05/17 12:15 PM, Logan Gunthorpe wrote:
> Hi,
> 
> On 27/05/17 12:08 PM, Geert Uytterhoeven wrote:
>> Still, those code patch could be protected by #ifdef CONFIG_HAS_IOMEM,
>> or better, if (IS_ENABLED(CONFIG_HAS_IOMEM)).
> 
> Well I think it would have to be the former seeing the latter would
> still end up trying to compile the missing function. But having ifdefs
> inside code is not generally seen as good idea[1].
> 
> I'd really like to go forward with either this patch or something like
> it. The other two arches that have this problem are fine with merging a
> fix and adding ifdefs to work around a single arch doesn't feel right to me.
> 
> Thanks,
> 
> Logan
> 
> [1] http://yarchive.net/comp/linux/ifdefs.html
> 


  reply	other threads:[~2017-06-08 18:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 15:42 [PATCH v2] um: add dummy ioremap and iounmap functions Logan Gunthorpe
2017-05-25 15:48 ` Richard Weinberger
2017-05-25 15:53   ` Logan Gunthorpe
2017-05-27 18:08     ` Geert Uytterhoeven
2017-05-27 18:15       ` Logan Gunthorpe
2017-06-08 18:53         ` Logan Gunthorpe [this message]
2017-06-08 19:17           ` Richard Weinberger
2017-06-21 21:25             ` Logan Gunthorpe
2017-06-21 21:30               ` Richard Weinberger
2017-06-21 21:31                 ` Logan Gunthorpe
2017-06-21 21:36                   ` Arnd Bergmann

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=348baf8d-b42f-13a7-3398-cb0268d7c693@deltatee.com \
    --to=logang@deltatee.com \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=sbates@raithlin.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=viro@zeniv.linux.org.uk \
    /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