From: "Du, Changbin" <changbin.du@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: changbin.du@intel.com, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org,
yamada.masahiro@socionext.com
Subject: Re: [PATCH 1/4] x86, build: Fact out fdimage/isoimage generation commands to standalone script
Date: Mon, 6 Nov 2017 10:58:50 +0800 [thread overview]
Message-ID: <20171106025849.GA1464@intel.com> (raw)
In-Reply-To: <20171105093208.5ncgz4o4klv3f3xn@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
On Sun, Nov 05, 2017 at 10:32:08AM +0100, Ingo Molnar wrote:
>
> A few spelling fixes:
>
> in the title:
>
> s/Fact out
> /Factor out
>
> * changbin.du@intel.com <changbin.du@intel.com> wrote:
>
> > From: Changbin Du <changbin.du@intel.com>
> >
> > The build message for fdimage/isoimage are pretty unstructured. The raw
> > shell command blocks are printed. We can improve them as regular build
> > system messages. Besides, writing commands in shell script is much more
> > easier than in a Makefile.
>
> s/much more easier
> /much more easy
>
> >
> > See Ingo's suggestion here https://lkml.org/lkml/2017/10/31/124.
> >
> > This patch fact out the commands used for fdimage/isoimage generation from
> > arch/x86/boot/Makefile to new script arch/x86/boot/genimage.sh. Then add a
> > new kbuild command 'genimage' which invokes the new script. All
> > fdimages/isoimage now is generated by call to 'genimage' with different
> > parameters.
>
> s/fact out
> /factors out
>
> s/to new script
> to a new script
>
> s/Then add
> /Then it adds
>
> s/a new kbuild command 'genimage'
> /the new 'genimage' kbuild command
>
> s/All fdimages/isoimage now is generated by call to
> /All fdimage/isoimage files are now generated by a call to
>
Sorry for these grammar errors. I alwyas forgot to write complete sentences in
English. :)
> > +# $3 - kernel bzImage file
> > +# $4 - mtool configuration file
> > +# $5 - kernel cmdline
> > +# $6 - inird image file
> > +#
>
> The new script is much easier to read!
>
> Thanks,
>
> Ingo
--
Thanks,
Changbin Du
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-11-06 3:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 9:18 [PATCH 0/4] x86, kbuild: Some improvements for fdimage/isoimage generation changbin.du
2017-11-05 9:18 ` [PATCH 1/4] x86, build: Fact out fdimage/isoimage generation commands to standalone script changbin.du
2017-11-05 9:32 ` Ingo Molnar
2017-11-06 2:58 ` Du, Changbin [this message]
2017-11-05 9:18 ` [PATCH 2/4] x86, build: Add new paths for isolinux.bin and ldlinux.c32 changbin.du
2017-11-05 9:33 ` Ingo Molnar
2017-11-06 3:00 ` Du, Changbin
2017-11-05 9:18 ` [PATCH 3/4] x86, build: Specify -input-charset=utf-8 for mkisofs changbin.du
2017-11-05 9:34 ` Ingo Molnar
2017-11-05 9:18 ` [PATCH 4/4] x86, boot: Add some generated files to the .gitignore file changbin.du
2017-11-05 9:37 ` [PATCH 0/4] x86, kbuild: Some improvements for fdimage/isoimage generation Ingo Molnar
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=20171106025849.GA1464@intel.com \
--to=changbin.du@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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