From: Michal Marek <mmarek@suse.cz>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
kyle@redhat.com, lacombar@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: REGRESSION: Re: [GIT] kconfig rc fixes
Date: Wed, 03 Nov 2010 23:47:21 +0100 [thread overview]
Message-ID: <4CD1E679.5080202@suse.cz> (raw)
In-Reply-To: <4CD1E232.30406@redhat.com>
On 3.11.2010 23:29, Mauro Carvalho Chehab wrote:
> Em 09-10-2010 18:40, Michal Marek escreveu:
>> The following changes since commit cb655d0f3d57c23db51b981648e452988c0223f9:
>>
>> Linux 2.6.36-rc7 (2010-10-06 13:39:52 -0700)
>>
>> are available in the git repository at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6.git rc-fixes
>>
>> Arnaud Lacombe (1):
>> kconfig: delay symbol direct dependency initialization
>
> This patch generated a regression with V4L build. After applying it, some Kconfig
> dependencies that used to work with V4L Kconfig broke.
You mean, the dependencies trigger a warning now, right? Also, you are
replying to my pull request for 2.6.36-rc8, but that pull request also
included "kconfig: Temporarily disable dependency warnings", so 2.6.36
final is NOT affected by this, just to clarify. 2.6.37-rc1 reverted this
workaround and I hope we come to some solution now. BTW,
http://www.kerneltrap.com/mailarchive/linux-kernel/2010/10/7/4629122/thread
is how a very similar issue was fixed in the i2c Kconfig (commit 0a57274
in 2.6.37-rc1 now).
Michal
next prev parent reply other threads:[~2010-11-03 22:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 22:40 [GIT] kconfig rc fixes Michal Marek
2010-11-03 22:29 ` REGRESSION: " Mauro Carvalho Chehab
2010-11-03 22:47 ` Michal Marek [this message]
2010-11-03 23:02 ` Mauro Carvalho Chehab
2010-11-04 2:31 ` Arnaud Lacombe
2010-11-04 3:19 ` Mauro Carvalho Chehab
2010-11-04 4:02 ` Arnaud Lacombe
2010-11-04 4:15 ` Arnaud Lacombe
2010-11-04 11:10 ` Mauro Carvalho Chehab
2010-11-04 17:19 ` Randy Dunlap
2010-11-04 18:11 ` Mauro Carvalho Chehab
2010-11-04 18:32 ` Arnaud Lacombe
2010-11-04 18:51 ` Mauro Carvalho Chehab
2010-11-05 12:02 ` Jean Delvare
2010-11-04 18:34 ` Arnaud Lacombe
2010-11-04 18:43 ` Mauro Carvalho Chehab
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=4CD1E679.5080202@suse.cz \
--to=mmarek@suse.cz \
--cc=kyle@redhat.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=torvalds@linux-foundation.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