All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Palms commits.
Date: Tue, 10 Jul 2007 22:01:28 +0100	[thread overview]
Message-ID: <1184101289.3683.7.camel@localhost.localdomain> (raw)
In-Reply-To: <48239d390707100845o17a49392vcbf74fd5991b77f3@mail.gmail.com>

Hi,

On Tue, 2007-07-10 at 19:45 +0400, Sergey Lapin wrote: 
> I just had raging argument with Paul Sokolovsky about my commits,
> so I'd like to RFC them, and also I'd like to ask if all these changes
> should be passed through RFC.
> 
> Please, see attachments. Sorry for post-factum.

I looked at the attachment and it does give me cause for concern.

What's missing from your email is a clear piece of text saying why
you're making the changes you are. Your commits are also a bit confused.
Updating a kernel defconfig in "Palm Zire 72 machine update" isn't very
obvious.

As for comments on specific things in the patch, in principle I agree
with common machine files and kernel updates. The
MACHINE_EXTRA_RRECOMMENDS in the patch looks horrendous however and it
does go against the principles of task-base and friends. 

Problems with the MACHINE_EXTRA_RRECOMMENDS include:

* the modules should have dependency information which removes the need
for all sound modules to be listed for example, you only need the ones
at the tips of the chains.
* duplication with entries already in task-base

The module_autoload statements also look scary. Is the device totally
incapable of loading some of them for itself? I know for a fact you
don't need all the sound ones.

Regards,

Richard




  parent reply	other threads:[~2007-07-10 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 15:45 [RFC] Palms commits Sergey Lapin
2007-07-10 18:16 ` Paul Sokolovsky
2007-07-10 19:11   ` Sergey Lapin
2007-07-10 19:58     ` Michael Krelin
2007-07-10 21:08     ` Paul Sokolovsky
2007-07-10 21:01 ` Richard Purdie [this message]
2007-07-11 12:59   ` Sergey Lapin

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=1184101289.3683.7.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 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.