From: Jamie Iles <jamie@jamieiles.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jamie Iles <jamie@jamieiles.com>,
linux-serial@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] tty: 8250_dw: fix build error for CONFIG_SERIAL_8250=m
Date: Wed, 24 Aug 2011 16:24:34 +0100 [thread overview]
Message-ID: <20110824152434.GQ23757@pulham.picochip.com> (raw)
In-Reply-To: <201108241645.16377.arnd@arndb.de>
Hi Arnd,
On Wed, Aug 24, 2011 at 04:45:16PM +0200, Arnd Bergmann wrote:
> When go go to such length, I think the approach I initially advocated
> (making 8250_dw a standalone platform_driver like of_serial) will be
> nicer.
For a separate driver, is it okay to make it depend on CONFIG_OF, and
only have device tree bindings, or should this still support being
registered as a static platform device with platform data? I'm not sure
what the consensus is on creating device tree only platform drivers.
Thanks,
Jamie
next prev parent reply other threads:[~2011-08-24 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 7:11 [PATCH] tty: 8250_dw: fix build error for CONFIG_SERIAL_8250=m Jamie Iles
2011-08-24 14:45 ` Arnd Bergmann
2011-08-24 14:54 ` Jamie Iles
2011-08-24 15:09 ` Greg KH
2011-08-24 15:12 ` Jamie Iles
2011-08-24 15:24 ` Jamie Iles [this message]
2011-08-24 16:14 ` 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=20110824152434.GQ23757@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-serial@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.