From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alan Cox <alan@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vincent Pelletier <plr.vincent@gmail.com>,
Simon Guinot <simon.guinot@sequanux.org>,
Giel van Schijndel <me@mortis.eu>,
linux-gpio@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vincent Donnefort <vdonnefort@gmail.com>,
Yoann Sculo <yoann@sculo.fr>
Subject: Re: [PATCH] kernel/resource.c: fix muxed resource handling in __request_region()
Date: Mon, 22 Feb 2016 12:46:09 -0800 [thread overview]
Message-ID: <56CB7391.30203@virtuousgeek.org> (raw)
In-Reply-To: <1456148952.24303.273.camel@linux.intel.com>
On 02/22/2016 05:49 AM, Alan Cox wrote:
>> we have some good alternatives in the form of bus and platform
>> drivers that
>> can manage the appropriate serialization and keep things from
>> stomping
>> on one another.
>
> It's not used much, especially nowdays. The use case is basically multi
> I/O chips on the ISA/LPC bus with magic shared config register ports.
>
> We have sufficiently few of those we could give muxed the boot and
> special case them if preferred.
Ah that's right, now I remember the context. So where should we go from here then? Just leave the ugly fix in or hack on old stuff and hope not to break it?
Jesse
next prev parent reply other threads:[~2016-02-22 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1440093809-18234-1-git-send-email-plr.vincent@gmail.com>
[not found] ` <7d1a2156ddabe0b72964e88734adba307a472067.1440093298.git.plr.vincent@gmail.com>
[not found] ` <20150821175216.GE1729@kw.sim.vm.gnt>
[not found] ` <20150821224824.3406caa0@x2>
[not found] ` <20150903200540.399a96b8@x2>
2015-09-09 22:01 ` [1/4] gpio: gpio-f7188x: Use mutex for access serialisation Simon Guinot
2015-09-09 22:15 ` [PATCH] kernel/resource.c: fix muxed resource handling in __request_region() Simon Guinot
2016-02-19 21:10 ` Vincent Pelletier
2016-02-19 23:25 ` Jesse Barnes
2016-02-20 17:11 ` Linus Torvalds
2016-02-20 22:15 ` Jesse Barnes
2016-02-22 13:49 ` Alan Cox
2016-02-22 20:46 ` Jesse Barnes [this message]
2016-02-23 16:19 ` Simon Guinot
2016-02-23 17:19 ` Jesse Barnes
2016-02-23 21:38 ` One Thousand Gnomes
2016-02-24 14:25 ` [PATCH] kernel/resource.c: ensure parent is not freed " Simon Guinot
2016-02-23 8:00 ` [PATCH] kernel/resource.c: fix muxed resource handling " Vincent Pelletier
2015-09-12 13:26 ` [1/4] gpio: gpio-f7188x: Use mutex for access serialisation Vincent Pelletier
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=56CB7391.30203@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=alan@linux.intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@mortis.eu \
--cc=plr.vincent@gmail.com \
--cc=simon.guinot@sequanux.org \
--cc=torvalds@linux-foundation.org \
--cc=vdonnefort@gmail.com \
--cc=yoann@sculo.fr \
/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).