From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Greg KH <greg@kroah.com>
Cc: Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH resend] Add sc16is7x2 driver
Date: Tue, 26 Oct 2010 20:28:42 +0100 [thread overview]
Message-ID: <20101026192842.GB7119@sirena.org.uk> (raw)
In-Reply-To: <20101026145107.GA18531@kroah.com>
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).
next prev parent reply other threads:[~2010-10-26 19:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 8:15 Manuel Stahl
2010-10-14 19:01 ` Greg KH
2010-10-15 7:24 ` Manuel Stahl
[not found] ` <20101015142709.GA18905@kroah.com>
2010-10-15 15:09 ` Manuel Stahl
2010-10-15 16:49 ` Greg KH
2010-10-18 9:46 ` Manuel Stahl
2010-10-19 15:37 ` Greg KH
2010-10-26 8:55 ` Manuel Stahl
2010-10-26 14:51 ` Greg KH
2010-10-26 14:59 ` Alan Cox
2010-10-26 19:28 ` Mark Brown [this message]
2010-11-08 14:01 ` Thomas Weber
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=20101026192842.GB7119@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
/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®