From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Horms <horms@verge.net.au>
Cc: linux-kernel@vger.kernel.org, fastboot@osdl.org, ebiederm@xmission.com
Subject: Re: [PATCH] kexec: typo in machine_kexec()
Date: Tue, 4 Apr 2006 20:05:57 -0700 [thread overview]
Message-ID: <20060404200557.1e95bdd8.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060404234806.GA25761@verge.net.au>
On Wed, 5 Apr 2006 08:48:08 +0900 Horms wrote:
> Signed-Off-By: Horms <horms@verge.net.au
>
> machine_kexec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Can you use diffstat -p1 ? does git allow/support that option, so that
more complete filenames are visible?
> b242c77f387d75d1bfa377d1870c0037d9e0c364
> diff --git a/arch/i386/kernel/machine_kexec.c b/arch/i386/kernel/machine_kexec.c
> index f73d737..beaad58 100644
> --- a/arch/i386/kernel/machine_kexec.c
> +++ b/arch/i386/kernel/machine_kexec.c
> @@ -194,7 +194,7 @@ NORET_TYPE void machine_kexec(struct kim
> * set them to a specific selector, but this table is never
> * accessed again you set the segment to a different selector.
> *
> - * The more common model is are caches where the behide
> + * The more common model is are caches where the behind
Also delete /are/, but that sentence and the previous one still need some
work, so fixing "behide" isn't a big deal IMO. However, Eric can decide
about the patch; he is the kexec maintainer.
> * the scenes work is done, but is also dropped at arbitrary
> * times.
> *
---
~Randy
next prev parent reply other threads:[~2006-04-05 3:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 23:48 Horms
2006-04-05 3:05 ` Randy.Dunlap [this message]
2006-04-05 5:56 ` Eric W. Biederman
2006-04-05 15:19 ` [PATCH] kexec: update MAINTAINERS Randy.Dunlap
2006-04-05 5:57 ` [PATCH] kexec: typo in machine_kexec() Horms
2006-04-05 6:24 ` Con Kolivas
2006-04-05 15:49 ` Eric W. Biederman
2006-04-05 17:09 ` Randy.Dunlap
2006-05-20 2:09 ` Horms
2006-04-05 3:10 ` Con Kolivas
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=20060404200557.1e95bdd8.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®