All of lore.kernel.org
 help / color / mirror / Atom feed
From: WANG Cong <xiyou.wangcong@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	mingo@redhat.com
Subject: Re: Incorrect filename comments in arch/x86/boot
Date: Fri, 25 Jan 2008 18:04:52 +0800	[thread overview]
Message-ID: <20080125100452.GH4726@hacking> (raw)
In-Reply-To: <47964FFC.9040601@zytor.com>

On Tue, Jan 22, 2008 at 12:20:12PM -0800, H. Peter Anvin wrote:
>Pavel Machek wrote:
>>Hi!
>>
>>Not sure if this is worth fixing, or if I should just delete those
>>comments...? (Or does someone want to do that? ;-). 
>>									Pavel
>
>I'll take care of it.
>

Hmm, arch/i386/boot/ is an empty dir. Why not remove it?
Only used to put bzImage? Why not choose another dir?
Maybe arch/x86/boot/, I think. ;)



      reply	other threads:[~2008-01-25 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 19:39 Incorrect filename comments in arch/x86/boot Pavel Machek
2008-01-22 20:20 ` H. Peter Anvin
2008-01-25 10:04   ` WANG Cong [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=20080125100452.GH4726@hacking \
    --to=xiyou.wangcong@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pavel@ucw.cz \
    /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.