linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Michal Marek <mmarek@suse.cz>,
	randy.dunlap@oracle.com, catalin.marinas@arm.com,
	linux-kbuild@vger.kernel.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, xiyou.wangcong@gmail.com
Subject: Re: [PATCH] Revert "kconfig: Temporarily disable dependency warnings"
Date: Thu, 25 Nov 2010 17:26:39 -0200	[thread overview]
Message-ID: <4CEEB86F.8070105@infradead.org> (raw)
In-Reply-To: <AANLkTi=io3tsuL8Hd2a0y8PyBYYAzb-gkJo1GfmpcF+L@mail.gmail.com>

Em 25-11-2010 15:16, Arnaud Lacombe escreveu:
> Hi,
> 
> On Sun, Nov 21, 2010 at 9:57 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi,
>>
>> On Sun, 21 Nov 2010 20:58:54 -0500 Arnaud Lacombe <lacombar@gmail.com> wrote:
>>>
>>> There is 2 patches which fixes that by adding to the kconfig language
>>> a "visible" property to menus, 1 revert of "another" solution (which
>>> works but does not scale) and 2 patch which makes usage of the new
>>> property. Ack-ed and complemented by Mauro, but still waiting
>>> review/blessing by Michal.
>>>
>>> The core change is available here: https://patchwork.kernel.org/patch/306412/
>>>
>>> Alternatively, if you don't care about the menu structure, Randy
>>> proposed a one-liner.
>>
>> OK, good to know it is being worked on.  Thanks.
>>
> FYI, I withdrawn the patches and ask for them not to be merged[0], as
> there is a clear lack of interest to see this issue resolved.
> 
> Mauro, may I ask you to remove my patches from:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git
> kconfig_fixes
> 
> please ?

I prefer to have them there, while the issue remains at .37/-next builds.

It is a pain to see all those warnings polluting my console, every time 
I recompile things, and I can't simply do a grep to discard MEDIA 
warnings/errors (as someone proposed), as this may prevent me to get real
errors at media builds.

The better is to give more time to Marek/Sam to review your patch
series and ack or, if they don't agree, to send an alternative patchset
to fix the issues or to revert the changeset that started to produce 
those troubles.

Cheers,
Mauro

      parent reply	other threads:[~2010-11-25 19:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06  0:44 linux-next: build warnings after merge of the kbuild-current tree Stephen Rothwell
2010-10-06 11:13 ` Michal Marek
2010-10-06 11:42   ` Catalin Marinas
2010-10-08 14:51     ` Michal Marek
2010-10-08 15:03       ` Américo Wang
2010-10-08 15:05         ` Michal Marek
2010-10-09 21:45         ` [PATCH] kconfig: Temporarily disable dependency warnings Michal Marek
2010-10-11 15:23           ` Catalin Marinas
2010-10-11 21:46             ` Michal Marek
2010-10-11 21:59               ` Randy Dunlap
2010-10-12 13:19                 ` [PATCH] Revert "kconfig: Temporarily disable dependency warnings" Michal Marek
2010-10-29  0:37                   ` Stephen Rothwell
2010-11-22  0:48                     ` Stephen Rothwell
2010-11-22  1:44                       ` Randy Dunlap
2010-11-22  1:58                       ` Arnaud Lacombe
2010-11-22  2:09                         ` Randy Dunlap
2010-11-22  2:17                           ` Arnaud Lacombe
2010-11-22  2:57                         ` Stephen Rothwell
2010-11-22 13:26                           ` Mauro Carvalho Chehab
2010-11-25 17:16                           ` Arnaud Lacombe
2010-11-25 17:43                             ` Catalin Marinas
2010-11-25 18:09                               ` Arnaud Lacombe
2010-11-26 12:33                                 ` Catalin Marinas
2010-11-26 13:33                                   ` Michal Marek
2010-11-26 14:50                                     ` Catalin Marinas
2010-11-25 19:26                             ` Mauro Carvalho Chehab [this message]

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=4CEEB86F.8070105@infradead.org \
    --to=mchehab@infradead.org \
    --cc=catalin.marinas@arm.com \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    --cc=xiyou.wangcong@gmail.com \
    /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).