From: Olof Johansson <olof@lixom.net>
To: Anand Gadiyar <gadiyar@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3: Fix omap3_defconfig build
Date: Thu, 10 Dec 2009 00:10:30 -0600 [thread overview]
Message-ID: <20091210061030.GA19668@lixom.net> (raw)
In-Reply-To: <1260424192-29012-1-git-send-email-gadiyar@ti.com>
Hi,
{removing invalid lkml-like addressee}
On Thu, Dec 10, 2009 at 11:19:52AM +0530, Anand Gadiyar wrote:
> Select sound codecs to allow this defconfig to build again
You need to fix the config option dependencies/selects, updating the
defconfig just papers over the real problem.
> Also, sync up this defconfig with the generated .configs.
Good idea, but I suggest holding off until the merge window has closed
since there are still new options going in. Doing a respin after -rc2
or so makes more sense. So please redo in a few weeks?
Traditionally Linus hasn't minded pulling in defconfig updates a little
later in the release cycles.
Thanks,
-Olof
next prev parent reply other threads:[~2009-12-10 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1260424192-29012-1-git-send-email-gadiyar@ti.com>
2009-12-10 6:01 ` [PATCH] OMAP3: Fix omap3_defconfig build Gadiyar, Anand
2009-12-10 6:10 ` Olof Johansson [this message]
2009-12-12 19:19 ` Tony Lindgren
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=20091210061030.GA19668@lixom.net \
--to=olof@lixom.net \
--cc=gadiyar@ti.com \
--cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox