From: Jaswinder Singh Rajput <jaswinder@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: x86 maintainers <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: reboot.c declare port_cf9_safe before they get used
Date: Mon, 29 Dec 2008 14:13:18 +0530 [thread overview]
Message-ID: <1230540199.3715.11.camel@jaswinder.satnam> (raw)
In-Reply-To: <20081227103141.GF14639@elte.hu>
Hello Ingo,
On Sat, 2008-12-27 at 11:31 +0100, Ingo Molnar wrote:
> btw., this is ugly now:
>
> > --- a/arch/x86/kernel/reboot.c
> > +++ b/arch/x86/kernel/reboot.c
> > @@ -22,6 +22,7 @@
> > #endif
> >
> > #include <mach_ipi.h>
> > +#include "../pci/pci.h"
>
> could you send another patch that moves arch/x86/pci/pci.h to
> arch/x86/include/asm/pci_x86.h (and update all the pci.h include sites)?
>
1. I send [PATCH] move arch/x86/pci/pci.h to
arch/x86/include/asm/pci_x86.h but I forget to write x86: before this
patch.
Please let me know which one is better option :
[PATCH]x86: move arch/x86/pci/pci.h to arch/x86/include/asm/pci_x86.h
OR
[PATCH -tip]x86: move arch/x86/pci/pci.h to
arch/x86/include/asm/pci_x86.h
OR some other name.
2. I also did not write any reason of patch this may lead confusion to
other developers, can you please provide some good reasons for this
patch.
3. I also did some cleanups in arch/x86/include/asm/pci_x86.h raised
by ./scripts/checkpatch.pl, is this OK.
4. Can I resend above patch by solving above issues.
Thank you,
JSR
next prev parent reply other threads:[~2008-12-29 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 16:21 Jaswinder Singh
2008-12-27 10:31 ` Ingo Molnar
2008-12-27 10:36 ` Jaswinder Singh Rajput
2008-12-29 8:43 ` Jaswinder Singh Rajput [this message]
2008-12-29 11:08 ` Ingo Molnar
2008-12-29 17:09 ` Jesse Barnes
2008-12-29 17:18 ` 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=1230540199.3715.11.camel@jaswinder.satnam \
--to=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@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®