From: Richard Weinberger <richard@nod.at>
To: Logan Gunthorpe <logang@deltatee.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "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: Wed, 21 Jun 2017 23:30:52 +0200 [thread overview]
Message-ID: <feb62ff1-2f1d-d6f6-208a-4c948bb8c479@nod.at> (raw)
In-Reply-To: <1d4d3148-fc88-f834-3881-16b85dafc8ef@deltatee.com>
Logan,
Am 21.06.2017 um 23:25 schrieb Logan Gunthorpe:
> Poke.
>
> On 08/06/17 01:17 PM, Richard Weinberger wrote:
>> Am 08.06.2017 um 20:53 schrieb Logan Gunthorpe:
>> IMHO an ifdef in scatterlist code does not hurt.
>> It is equally ugly than mocking ioremap for UML.
>
> I disagree. Having ifdefs scattered around all call sites of a function
> is *much* worse than having an extra mock function tucked away in a
> header file somewhere.
>
> It's a very common pattern in the kernel for providers of functions that
> depend on a configuration option to provide mock functions when the
> configuration option is not selected. This prevents needing every caller
> of said function to put #ifdefs around the call. For a few examples:
>
> include/linux/blkdev.h:1952
> include/linux/dax.h:24
> include/linux/pci.h:1329
>
> And, frankly, it's _exactly_ what Linus Torvalds himself was arguing
> against in the link I sent up-thread [1].
>
>> So, I'm puzzled.
>> Arnd, what do you think?
>> Shall !HAS_IOMEM archs just mock these functions?
>
> So, once again, 'um' is now the only architecture that has this problem
> since tile and s390 accepted my patches (and without a fuss too). So can
> you please consider merging this patch or proposing something that will
> also fix the problem?
Since Arnd stays silent and um is the only remaining odd-ball, let's merge this
in v4.13.
Thanks,
//richard
next prev parent reply other threads:[~2017-06-21 21:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 15:42 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
2017-06-08 19:17 ` Richard Weinberger
2017-06-21 21:25 ` Logan Gunthorpe
2017-06-21 21:30 ` Richard Weinberger [this message]
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=feb62ff1-2f1d-d6f6-208a-4c948bb8c479@nod.at \
--to=richard@nod.at \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--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
all inboxes | Powered by JetHome®