From: broonie@opensource•wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: S3C64XX: Update configuration for WM5102 module on Cragganmore
Date: Thu, 23 Aug 2012 16:20:31 +0100 [thread overview]
Message-ID: <20120823152031.GH7995@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1d5901cd8114$023550f0$069ff2d0$%kim@samsung.com>
On Thu, Aug 23, 2012 at 06:45:19PM +0900, Kukjin Kim wrote:
> Yeah, actually SoC defconfig in mainline doesn't cover _real_ requirements
> for (mass) product. But I think, it's time we need to sort out the
> defconfigs so that we could use them efficiently on product. BTW, if
> enabling board in defconfig, at least, unexpected build breakages could be
> detected by testing defconfig before merge for mainline...
Right, sure. I guess the main thing I'm saying here is that I don't
mind what happens here, it's certainly no problem for me turn them on in
the build if that's what people wants.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120823/0be86153/attachment.sig>
next prev parent reply other threads:[~2012-08-23 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 18:05 [PATCH 1/2] ARM: S3C64XX: Update configuration for WM5102 module on Cragganmore Mark Brown
2012-08-09 18:05 ` [PATCH 2/2] ARM: S3C64XX: Register audio platform devices for Bells " Mark Brown
2012-08-10 4:56 ` [PATCH 1/2] ARM: S3C64XX: Update configuration for WM5102 module " Kukjin Kim
2012-08-10 10:07 ` Mark Brown
2012-08-11 5:08 ` Kukjin Kim
2012-08-13 12:24 ` Mark Brown
2012-08-23 9:45 ` Kukjin Kim
2012-08-23 15:20 ` Mark Brown [this message]
2012-08-28 23:30 ` Kukjin Kim
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=20120823152031.GH7995@opensource.wolfsonmicro.com \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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