linux-kernel - Re: [PATCH resend] Add sc16is7x2 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101026192842.GB7119@sirena.org.uk>
Date:	Tue, 26 Oct 2010 20:28:42 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Greg KH <greg@...ah.com>
Cc:	Manuel Stahl <manuel.stahl@....fraunhofer.de>,
	linux-serial@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH resend] Add sc16is7x2 driver

On Tue, Oct 26, 2010 at 07:51:07AM -0700, Greg KH wrote:
> On Tue, Oct 26, 2010 at 10:55:24AM +0200, Manuel Stahl wrote:

> > This is the driver I took as a template. It consists of 
> > drivers/serial/max3100.c and include/linux/serial_max3100.h

> > And huh, "grep -R serial_max3100.h *" gives what? Only max3100.c
> > So do we need to remove serial_max3100.h as it's not used anywhere else?

> Yup, that sounds like a great idea, I'll go queue up that patch when I
> get back from my travels at the moment.

Requiring that we have a user for all platform data provided by drivers
would be incredibly painful for embedded development.  It would mean
that we would be unable to usefully merge any drivers with platform data
unless we also merge at least one board using them, meaning that we're
dependant on getting the core board support for some public board into a
state which can be merged (which would at best be likely to end up
creating logjams on support for CPUs).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/