All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Tim Bird <tim.bird@am.sony.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: ANNOUNCE: CE Linux Forum - Specification V1.0 draft
Date: Wed, 19 May 2004 17:27:06 +0200	[thread overview]
Message-ID: <20040519152706.GD22742@fs.tum.de> (raw)
In-Reply-To: <40A92D15.2060006@am.sony.com>

On Mon, May 17, 2004 at 02:22:29PM -0700, Tim Bird wrote:
> Christoph Hellwig wrote:
> >On Mon, May 17, 2004 at 12:05:36PM -0700, Tim Bird wrote:
> >
> >>I am writing to announce the availability of the first draft of
> >>the CE Linux Forum's first specification.  This specification
> >>represents the efforts of six different technical working groups
> >>over about the last 9 months.
> >
> >
> >If you want my 2Cent:
> >
> > - stop these rather useless specifications and provide patchkits instead
> > - try to actually submit the patches upstream to get a feeling which
> >   of your 'features' are compltely hopeless, which are okay and which
> >   can better be solved in different ways.
> 
> I should point out that some of the features specified have already been
> submitted as patchsets.  Some were accepted and are in 2.6.  Some were
> rejected, and we are considering the feedback received...  (But, we're
> still hopeful that in the long run, we can make certain things
> acceptable for inclusion in the mainline tree.)
> 
> The submissions, so far, have come from member companies or individuals
> rather than from the forum itself.

A good example that this is true is section 7.9.2 of your 
"specification".

It lists under "Work in Progress":
  Kernel SHALL be configuralble with compiler size options, such as -Os.

Besides the text in the "Rationale" being obviously wrong, this is 
already implemented in kernel 2.6. But the people writing this
"specification" didn't send a patch - the trivial patch was sent by 
someone who is in no way related to your "Forum".

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-05-19 15:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 19:05 ANNOUNCE: CE Linux Forum - Specification V1.0 draft Tim Bird
2004-05-17 19:19 ` Christoph Hellwig
2004-05-17 19:59   ` Tim Bird
2004-05-17 20:42   ` Mark Gross
2004-05-17 20:48     ` Arjan van de Ven
     [not found]     ` <20040518074854.A7348@infradead.org>
2004-05-18 19:32       ` Mark Gross
2004-05-18 19:56         ` Russell King
2004-05-18 20:45           ` Bartlomiej Zolnierkiewicz
2004-05-18 20:00         ` viro
2004-05-19 19:30       ` Tim Bird
2004-05-19 21:57         ` Russell King
2004-05-19 22:02           ` Jeff Garzik
2004-05-19 23:46           ` Tim Bird
2004-05-19 22:08         ` Theodore Ts'o
2004-05-19 23:37           ` Tim Bird
2004-05-17 21:22   ` Tim Bird
2004-05-19 15:27     ` Adrian Bunk [this message]
2004-05-19 16:59       ` Tim Bird
2004-05-19 20:16         ` Adrian Bunk
2004-05-19 20:38           ` Tim Bird
2004-05-19 20:48             ` Nicolas Pitre
2004-05-19 22:00         ` Russell King

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=20040519152706.GD22742@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@am.sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.