public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Brown, Len" <len.brown@intel.com>
Cc: Len Brown <lenb@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"stable@kernel.org" <stable@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: build warningiIn Linus' tree
Date: Mon, 30 May 2011 21:23:44 +0200	[thread overview]
Message-ID: <20110530192344.GA5393@elte.hu> (raw)
In-Reply-To: <E87738D94A6AD54789B5B8D1BAEB06CC701ED3BA3E@azsmsx503.amr.corp.intel.com>


* Brown, Len <len.brown@intel.com> wrote:

> Alan convinced me that the community doesn't move that fast, and 
> that we should wallow in the swill for a while longer before 
> deleting. [...]

Yeah, it's much nicer this way.

> [...] Others volunteered to test the latest upstream kernel on APM 
> hardware, giving APM's presence in the upstream kernel a life line. 
> So all I did was add the recommended feature-removal's and warnings 
> for the stuff which obviously should go.  But if you see some of 
> your favorite bits on the chopping block, you have at least 6 
> months to make a case for them :-)

:-)

I only saw one of the runtime warnings on one of my testboxes - i 
adjusted the boot parameter setting (the parameter was bogus) and 
moved on. So life can go on as far as i'm involved :-)

Thanks,

	Ingo

      reply	other threads:[~2011-05-30 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  1:48 linux-next: build warningiIn Linus' tree Stephen Rothwell
2011-05-30  3:47 ` Len Brown
2011-05-30  7:34   ` Ingo Molnar
2011-05-30 19:11     ` Brown, Len
2011-05-30 19:23       ` Ingo Molnar [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=20110530192344.GA5393@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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