Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC v3 PATCH 0/9] Linux 3.0 build support
Date: Thu, 30 Jun 2011 09:00:44 +0100	[thread overview]
Message-ID: <1309420844.20015.426.camel@rex> (raw)
In-Reply-To: <BANLkTi=9ngg0yFnggOKLuccsdA7jTwTaZw@mail.gmail.com>

On Wed, 2011-06-29 at 20:02 +0200, Anders Darander wrote:
> On Wed, Jun 29, 2011 at 19:54, Anders Darander <anders@chargestorm.se> wrote:
> >
> > v3: - task-base.bb: fix a problem that *pcmia26 couldn't be found.
> 
> This third version fixes a bug introduced in v2. (task-base-pcmcia26
> weren't found). The fix is incorporated in patch 0008 (task-base).
> 
> Sofar, I've only got positive feedback on v2. (some feedback off-list
> (including some that probably should have been on-list if it hadn't
> been for some gmane problems).
> 
> Unless I find some more problems, or get such reports, I plan to send
> a pull request towards the end of this week.

It looks good to me apart from some ordering and PR bump type issues. 

Where you change the depmod dependency for example, we really need to
rebuild module-init-tools at the same time so the binary changes name at
the right point in the series. Patch 4 and patch 2 therefore probably
need to be together with a PR bump. I also wondered what the patch to
module-init-tools you're removing does (and why you just disabled rather
than deleted it).

Looks good though! I'm trying to resist merging some of the standalone
bits straight away :)

Cheers,

Richard




  reply	other threads:[~2011-06-30  8:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 17:54 [RFC v3 PATCH 0/9] Linux 3.0 build support Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 1/9] Remove support for building 2.4 kernels Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 2/9] image¡kernel.bblass: do not use depmod-2.6 Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 3/9] modules-init-tools(-cross): update to 3.16 Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 4/9] module-init-tools-cross: do not install depmod as depmod-2.6 Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 5/9] kernel.bblass: remove get_kernelmajorversion Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 6/9] modutils-initscripts: move recipe prior to modutils removal Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 7/9] modutils: remove modutils Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 8/9] task-base: remove modutils reference Anders Darander
2011-06-29 17:54 ` [RFC v3 PATCH 9/9] distro_tracking_fields: remove modutils Anders Darander
2011-06-29 18:02 ` [RFC v3 PATCH 0/9] Linux 3.0 build support Anders Darander
2011-06-30  8:00   ` Richard Purdie [this message]
2011-06-30  9:20     ` Anders Darander

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=1309420844.20015.426.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox