From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
Sam Ravnborg <sam@ravnborg.org>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
tabbott@ksplice.com, vda.linux@googlemail.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
heiko.carstens@de.ibm.com, schwidefsky@de.ibm.com
Subject: Re: [PATCH 0/2] initramfs: Cleanup and fix initramfs size calculation
Date: Tue, 07 Sep 2010 14:25:13 -0700 [thread overview]
Message-ID: <4C86ADB9.8030401@linux.intel.com> (raw)
In-Reply-To: <4C7D0CDB.6030903@suse.cz>
On 08/31/2010 07:08 AM, Michal Marek wrote:
> On 31.8.2010 10:23, Hendrik Brueckner wrote:
>> Hello Michal, Sam,
>>
>> I did not see any further comments on the patch series about the
>> initramfs cleanup and new size calculation.
>
> Sorry about that, I don't always have as much time for kbuild as I would
> like to have :(.
>
>
>> This is a resend and now I am asking you for your review and ack.
>> Please let me know if you have questions or comments.
>
> I like the cleanup patch and the thing still survives (very basic)
> testing, so
> Acked-by: Michal Marek <mmarek@suse.cz>
>
> I'm wondering which tree should these patches go through... Peter, will
> you apply them to some branch of tip.git or should I apply them to
> kbuild-2.6.git?
>
[Sorry for late reply, I have been away]
It's up to you, but I'm happy to apply them to a tip branch with your ack.
-hpa
prev parent reply other threads:[~2010-09-07 21:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 8:23 [PATCH 0/2] initramfs: Cleanup and fix initramfs size calculation Hendrik Brueckner
2010-08-31 8:23 ` [PATCH 1/2] initramfs: Generalize initramfs_data.xxx.S variants Hendrik Brueckner
2010-08-31 8:23 ` [PATCH 2/2] initramfs: Fix initramfs size calculation Hendrik Brueckner
2010-09-01 7:47 ` Américo Wang
2010-10-17 18:28 ` Mike Frysinger
2010-10-18 10:37 ` Hendrik Brueckner
2010-10-18 23:07 ` Mike Frysinger
2010-10-19 11:08 ` [PATCH] initramfs: Fix build break on symbol-prefixed archs Hendrik Brueckner
2010-10-19 20:11 ` Mike Frysinger
2010-10-19 21:31 ` Sam Ravnborg
2010-10-19 21:39 ` Mike Frysinger
2010-10-27 18:23 ` Mike Frysinger
2010-10-27 22:46 ` Michal Marek
2010-10-27 23:10 ` Mike Frysinger
2010-10-27 23:33 ` Michal Marek
2010-10-27 23:58 ` Mike Frysinger
2010-10-28 12:08 ` Michal Marek
2010-10-28 19:46 ` Mike Frysinger
2010-10-28 19:51 ` Mike Frysinger
2010-10-28 20:35 ` Sam Ravnborg
2010-10-28 20:42 ` Mike Frysinger
2010-10-28 20:53 ` Mike Frysinger
2010-10-29 6:12 ` Sam Ravnborg
2010-10-28 21:19 ` Michal Marek
2010-11-13 23:17 ` Mike Frysinger
2010-11-24 8:40 ` Mike Frysinger
2010-11-29 22:38 ` Andrew Morton
2010-11-29 23:29 ` Mike Frysinger
2010-11-30 15:36 ` Michal Marek
2010-12-02 4:12 ` Mike Frysinger
2010-08-31 14:08 ` [PATCH 0/2] initramfs: Cleanup and fix initramfs size calculation Michal Marek
2010-09-07 21:25 ` H. Peter Anvin [this message]
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=4C86ADB9.8030401@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.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