All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/4] lvm2.inc: add machine specific configuration file
Date: Mon, 26 Jul 2010 09:46:43 +0200	[thread overview]
Message-ID: <20100726074643.GC27921@excalibur.local> (raw)
In-Reply-To: <1279651497-20918-4-git-send-email-morphis@gravedo.de>

On Tue, 2010-07-20 at 20:44, Simon Busch wrote:
> For some machines we need a specific lvm configuration to detect the captable devices
> which can contain a lvm volume.
> 
> Signed-off-by: Simon Busch <morphis@gravedo.de>

Acked-by: Stefan Schmidt <stefan@datenfreihafen.org>



  reply	other threads:[~2010-07-26  7:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 18:44 Some love for the lvm2 recipes Simon Busch
2010-07-20 18:44 ` [PATCH 1/4] lvm2: rebase all recipes on a global lvm2.inc recipe Simon Busch
2010-07-26  7:46   ` Stefan Schmidt
2010-07-26 19:58     ` Simon Busch
2010-07-28 13:44       ` Stefan Schmidt
2010-07-28 17:20         ` Simon Busch
2010-07-28 18:07           ` Stefan Schmidt
2010-08-10 15:51             ` Simon Busch
2010-08-13 21:57             ` Stefan Schmidt
2010-07-20 18:44 ` [PATCH 2/4] lvm2.inc: add patch to fix building Simon Busch
2010-07-26  7:46   ` Stefan Schmidt
2010-07-20 18:44 ` [PATCH 3/4] lvm2.inc: add machine specific configuration file Simon Busch
2010-07-26  7:46   ` Stefan Schmidt [this message]
2010-07-20 18:44 ` [PATCH 4/4] lvm2: add configuration file for palmpre machine Simon Busch
2010-07-26  7:47   ` Stefan Schmidt
2010-08-10 15:44 ` [PATCH 5/5] lvm2.inc: remove unnecessary EXTRA_OECONF_arm line from recipe Simon Busch
2010-08-13 21:55   ` Stefan Schmidt
2010-08-16 13:59     ` Stefan Schmidt
2010-08-16 17:52       ` Simon Busch

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=20100726074643.GC27921@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --cc=openembedded-devel@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 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.