From: Mark Brown <broonie@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tushar Behera <tushar.behera@linaro.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
jslaby <jslaby@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: Re: [PATCH 1/2] serial: samsung: Move uart_register_driver call to device probe
Date: Tue, 21 Jan 2014 16:59:35 +0000 [thread overview]
Message-ID: <20140121165935.GB17314@sirena.org.uk> (raw)
In-Reply-To: <20140120234734.11b78578@www.etchedpixels.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]
On Mon, Jan 20, 2014 at 11:47:34PM +0000, Alan Cox wrote:
> Mark Brown <broonie@kernel.org> wrote:
> > On Mon, Jan 20, 2014 at 09:43:05PM +0000, Alan Cox wrote:
> > The userspace breakage is that if someone has a static /dev that doesn't
> > handle any dynamic devices then renumbering the device will cause that
> > static /dev to stop matching the kernel.
> Diddums and you've only provided theoretical cases not real world ones.
I'm fairly sure I have some older boards on my desk with static /dev,
I'd need to go and check which is rather more effort than I'm interested
in putting in for point scoring.
> They should have followed proper practice and reserved their minors. The
> device number belongs to the Altix. The driver should just move.
They should have done that about a decade ago when this stuff was
introduced, yes. At some point one has to accept and deal with the
world as it is.
> But yes I agree about the idiom, but a definite NAK to any attempts to
> plaster over this grand screwup by crapping in the tty core. Your turd,
> deal with it locally in the ARM code if you can't apply common sense and
> just go dynamic.
Local bodges being the first two patches Greg knocked back of course...
In any case, if we can convince people to make the subsystem better and
coincidentally also stop problems occuring on their systems that does
seem like a win overall.
> And please, after screwing this up twice - *learn* from the mess.
One of the things we've been trying to do is to ensure that the all the
driver code that isn't core architecture support (not just for ARM, for
everything) is going into subsystems so we're getting good review from
people who actually know the subsystems and aren't just saying things
are random platform stuff or whatever that we don't care about. That
has been a source of problems all over, we're trying to avoid it.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-21 17:00 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 9:02 [PATCH 0/2] serial: " Tushar Behera
2014-01-20 9:02 ` [PATCH 1/2] serial: samsung: " Tushar Behera
2014-01-20 10:05 ` Russell King - ARM Linux
2014-01-20 11:53 ` Tushar Behera
2014-01-20 12:26 ` Russell King - ARM Linux
2014-01-20 21:43 ` Alan Cox
2014-01-20 23:14 ` Mark Brown
2014-01-20 23:21 ` Russell King - ARM Linux
2014-01-20 23:35 ` Alan Cox
2014-01-20 23:52 ` Greg Kroah-Hartman
2014-01-20 23:47 ` Alan Cox
2014-01-21 0:16 ` Russell King - ARM Linux
2014-01-21 9:03 ` Alan Cox
2014-01-21 9:49 ` Russell King - ARM Linux
[not found] ` <50b66ac6-1150-4ad7-aeaf-3d0dce77334d@email.android.com>
2014-01-26 11:54 ` Russell King - ARM Linux
2014-01-27 4:30 ` Nicolas Pitre
2014-01-27 10:07 ` Alan Cox
2014-01-27 12:32 ` Russell King - ARM Linux
2014-01-27 15:03 ` Nicolas Pitre
2014-01-21 16:59 ` Mark Brown [this message]
2014-01-21 18:30 ` Russell King - ARM Linux
2014-01-23 18:04 ` Alan Cox
2014-01-23 18:40 ` Mark Brown
2014-01-23 18:47 ` Tomasz Figa
2014-01-23 19:36 ` Mark Brown
2014-01-23 19:51 ` Alan Cox
2014-01-23 20:05 ` Mark Brown
2014-01-23 21:33 ` Alan Cox
2014-01-24 12:03 ` Mark Brown
2014-01-24 14:38 ` Alan Cox
2014-01-27 0:15 ` Mark Brown
2014-01-26 21:09 ` Pavel Machek
2014-01-27 0:04 ` Alan Cox
2014-01-20 21:16 ` Greg KH
2014-01-20 21:32 ` Russell King - ARM Linux
2014-01-20 23:11 ` Greg KH
2014-01-20 23:16 ` Russell King - ARM Linux
2014-01-20 23:51 ` Greg KH
2014-01-21 0:07 ` Russell King - ARM Linux
2014-01-21 0:26 ` Greg KH
2014-01-21 0:38 ` Russell King - ARM Linux
2014-01-21 9:25 ` One Thousand Gnomes
2014-01-21 9:45 ` Russell King - ARM Linux
2014-01-20 9:02 ` [PATCH 2/2] serial: pl011: " Tushar Behera
2014-01-20 10:04 ` Russell King - ARM Linux
2014-02-13 18:12 ` Greg KH
2014-02-13 18:15 ` Russell King - ARM Linux
2014-02-13 18:27 ` Greg KH
2014-02-13 18:42 ` Russell King - ARM Linux
2014-02-13 23:26 ` Greg KH
2014-02-14 0:07 ` Russell King - ARM Linux
2014-02-14 0:14 ` Greg KH
2014-02-14 0:38 ` Russell King - ARM Linux
2014-02-17 15:35 ` One Thousand Gnomes
2014-02-17 15:54 ` One Thousand Gnomes
2014-02-17 23:50 ` Mark Brown
2014-02-18 10:09 ` Etched Pixels
2014-02-19 13:57 ` Mark Brown
2014-02-19 14:47 ` One Thousand Gnomes
2014-02-19 15:53 ` Mark Brown
2014-02-19 0:47 ` One Thousand Gnomes
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=20140121165935.GB17314@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben.dooks@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tushar.behera@linaro.org \
/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®