From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>, "Brown, Len" <len.brown@intel.com>,
Adrian Bunk <bunk@stusta.de>, Zachary Amsden <zach@vmware.com>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
Rusty Russell <rusty@rustcorp.com.au>, Jack Lo <jlo@vmware.com>,
v4l-dvb-maintainer@linuxtv.org, linux-acpi@vger.kernel.org
Subject: Re: Options depending on STANDALONE
Date: Thu, 3 Aug 2006 14:41:47 -0700 [thread overview]
Message-ID: <20060803214147.GA20468@kroah.com> (raw)
In-Reply-To: <20060803210130.GJ16927@redhat.com>
On Thu, Aug 03, 2006 at 05:01:30PM -0400, Dave Jones wrote:
> On Thu, Aug 03, 2006 at 01:51:27PM -0700, Greg Kroah-Hartman wrote:
> > On Thu, Aug 03, 2006 at 04:49:08PM -0400, Brown, Len wrote:
> > > I've advised SuSE many times that they should not be shipping it,
> > > as it means that their supported OS is running on modified firmware --
> > > which, by definition, they can not support. Indeed, one could view
> > > this method as couter-productive to the evolution of Linux --
> > > since it is our stated goal to run on the same machines that Windows
> > > runs on -- without requiring customers to modify those machines
> > > to run Linux.
> >
> > Ok, if it's your position that we should not support this, I'll see what
> > I can do to remove it from our kernel tree...
> >
> > If there are any other patches that we are carrying that you (or anyone
> > else) feel we should not be, please let me know.
>
> It's somewhat hard to tell when the source rpm's don't match the binaries.
> See ftp://ftp.suse.com/pub/projects/kernel/kotd/x86_64/HEAD for example,
> and notice the lack of 2.6.18rc3 source, just 2.6.16. Or am I looking
> in the wrong place ? (The other arch's all seem to suffer this curious problem).
Bleah, our KOTD build is still broken...
We do have a 2.6.18rc3 kernel, and everything rebased on that, but it's
not getting out to the world just yet for some odd reason. It will show
up in the next Opensuse 10.2 Alpha release some time next week, but it
should be mirroring nightly too.
/me goes off to kick the build system
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-03 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 20:49 Options depending on STANDALONE Brown, Len
2006-08-03 20:51 ` Greg KH
2006-08-03 21:01 ` Dave Jones
2006-08-03 21:41 ` Greg KH [this message]
2006-08-07 17:33 ` Thomas Renninger
2006-08-07 17:56 ` Greg KH
2006-08-07 18:46 ` Eric Piel
2006-08-08 11:00 ` Thomas Renninger
[not found] <44D1CC7D.4010600@vmware.com>
[not found] ` <1154603822.2965.18.camel@laptopd505.fenrus.org>
[not found] ` <44D23B84.6090605@vmware.com>
[not found] ` <20060803190327.GA14237@kroah.com>
[not found] ` <44D24B31.2080802@vmware.com>
[not found] ` <20060803193600.GA14858@kroah.com>
[not found] ` <20060803195617.GD16927@redhat.com>
2006-08-03 20:25 ` Adrian Bunk
2006-08-03 20:28 ` Greg KH
2006-08-03 20:41 ` Dave Jones
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=20060803214147.GA20468@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=hch@infradead.org \
--cc=jlo@vmware.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=zach@vmware.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).