From: jassisinghbrar@gmail.com (jassi brar)
To: linux-arm-kernel@lists.infradead.org
Subject: Problems with device compilation by subsystem config
Date: Thu, 28 Jan 2010 16:27:54 +0900 [thread overview]
Message-ID: <1b68c6791001272327y79b6cc98g56ddcdf015766c36@mail.gmail.com> (raw)
In-Reply-To: <20100128070518.GS10014@trinity.fluff.org>
On Thu, Jan 28, 2010 at 4:05 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> To fix thsi I propose changing the SPI and Audio support to have their
> own 'config S3C_DEV_xxx' entries which are selected by the boards that
> use them (this removes the need for #ifdef in the board file) and these
> entries should not be dependant on the subsytem defines.
I see the point.
I am preparing patches for new machine selectable config options for SPI and
AUDIO (even though I am not the original author of dev-audio.c but Mark
can always NAK the patch if he disagrees)
next prev parent reply other threads:[~2010-01-28 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:05 Problems with device compilation by subsystem config Ben Dooks
2010-01-28 7:27 ` jassi brar [this message]
2010-01-28 9:32 ` Mark Brown
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=1b68c6791001272327y79b6cc98g56ddcdf015766c36@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).