mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaswinder Singh <jaswinder@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	torvalds@linux-foundation.org,
	kernelnewbies <kernelnewbies@nl.linux.org>,
	kernel-janitors <kernel-janitors@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] x86-kernel: declare some functions before they get used
Date: Sun, 20 Jul 2008 23:42:07 +0530	[thread overview]
Message-ID: <1216577527.2706.13.camel@jaswinder.satnam> (raw)
In-Reply-To: <20080720174018.GA16827@elte.hu>

Hello Ingo,

On Sun, 2008-07-20 at 19:40 +0200, Ingo Molnar wrote:
> * Jaswinder Singh <jaswinder@infradead.org> wrote:
> 
> > x86-kernel: declare some functions before they get used
> 
> i like this cleanup - would you mind to do a version of this patch that 
> applies to Linus's latest -git tree?
> 

I divided this patch into many parts.

You already applied '[PATCH] x86: Introducing asm-x86/traps.h' to tip/x86/core.

and '[PATCH] Introducing asm/syscalls.h' is on the floor, I
received Acked-by: Ralf Baechle <ralf@linux-mips.org> and waiting for
other Acks.

If you merge '[PATCH] Introducing asm/syscalls.h' to
your tip/x86/core then I will send you updated patch of '[PATCH]
x86-kernel: declare some functions before they get used' based upon on
your latest tip/x86/core git tree.

If Linus add this '[PATCH] Introducing asm/syscalls.h' in his tree
then I will send you updated patch of '[PATCH] x86-kernel: declare some
functions before they get used' based upon on latest Linus git tree.

Please let me know which option is better.

Thank you,

Jaswinder Singh.


      reply	other threads:[~2008-07-20 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 15:56 Jaswinder Singh
2008-07-20 17:40 ` Ingo Molnar
2008-07-20 18:12   ` Jaswinder Singh [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=1216577527.2706.13.camel@jaswinder.satnam \
    --to=jaswinder@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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®