public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>,
	tabbott@ksplice.com, vda.linux@googlemail.com, mmarek@suse.cz,
	hpa@linux.intel.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, heiko.carstens@de.ibm.com,
	brueckner@linux.vnet.ibm.com, schwidefsky@de.ibm.com
Subject: [PATCH v2 0/2] initramfs: Cleanup and fix initramfs size calculation
Date: Thu, 26 Aug 2010 13:41:22 +0200	[thread overview]
Message-ID: <20100826114122.292120483@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100825180601.GA2116@merkur.ravnborg.org>

On Wed, Aug 25, 2010 at 08:06:01PM +0200, Sam Ravnborg wrote:
> On Wed, Aug 25, 2010 at 05:57:12PM +0200, Michael Holzheu wrote:
>
> > The patch also restructures the "usr/initramfs_data.xxx.S" files to use a
> > common macro that includes the (compressed) initramfs file and calculates
> > the __initramfs_size.
> I like this anyway. Could you do this as a separate patch?

Done ;-)

The first patch in this series introduces a common initramfs_data.S file
that is shared by the compression variants.  The second patch adds the new
initramfs size calculation proposed in the initial patch.
See the patch description for more details.


Kind regards,
  Hendrik

  parent reply	other threads:[~2010-08-26 11:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 15:57 [PATCH] Fix initramfs size calculation Michael Holzheu
2010-08-25 18:06 ` Sam Ravnborg
2010-08-25 19:15   ` Hendrik Brueckner
2010-08-25 19:56     ` Sam Ravnborg
2010-08-26  8:55       ` Michael Holzheu
2010-08-26 11:41   ` Hendrik Brueckner [this message]
2010-08-26 11:41   ` [PATCH v2 1/2] initramfs: Generalize initramfs_data.xxx.S variants Hendrik Brueckner
2010-08-26 11:41   ` [PATCH v2 2/2] initramfs: Fix initramfs size calculation Hendrik Brueckner
2010-08-25 20:10 ` [PATCH] " H. Peter Anvin
2010-08-26  8:46   ` Michael Holzheu

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=20100826114122.292120483@linux.vnet.ibm.com \
    --to=brueckner@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tabbott@ksplice.com \
    --cc=vda.linux@googlemail.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