From: Andi Kleen <ak@suse.de>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net, kaos@sgi.com
Subject: Re: [Lse-tech] [PATCH 4/7]: changes notifier head of diechains and add notify_chain_unregister
Date: Thu, 24 Nov 2005 00:57:28 +0100 [thread overview]
Message-ID: <20051123235728.GB31722@brahms.suse.de> (raw)
In-Reply-To: <1132789192.9460.20.camel@linuxchandra>
> Index: l2615-rc1-notifiers/include/asm-x86_64/kdebug.h
> ===================================================================
> --- l2615-rc1-notifiers.orig/include/asm-x86_64/kdebug.h
> +++ l2615-rc1-notifiers/include/asm-x86_64/kdebug.h
> @@ -5,21 +5,20 @@
>
> struct pt_regs;
>
> -struct die_args {
> +struct die_args {
etc. lots more occurrences.
Can you please repost the patch without arbitary white space changes
everywhere? They make it hard to review what you actually changed.
-Andi
next prev parent reply other threads:[~2005-11-23 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 23:39 [PATCH 4/7]: changes notifier head of diechains and add notify_chain_unregister Chandra Seetharaman
2005-11-23 23:57 ` Andi Kleen [this message]
2005-11-25 4:31 ` [Lse-tech] " Keith Owens
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=20051123235728.GB31722@brahms.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=sekharan@us.ibm.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