From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh <jaswinder@infradead.org>
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 17:40:18 +0000 [thread overview]
Message-ID: <20080720174018.GA16827@elte.hu> (raw)
In-Reply-To: <1216050964.2719.4.camel@jaswinder.satnam>
* 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?
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh <jaswinder@infradead.org>
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 19:40:18 +0200 [thread overview]
Message-ID: <20080720174018.GA16827@elte.hu> (raw)
In-Reply-To: <1216050964.2719.4.camel@jaswinder.satnam>
* 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?
Ingo
next prev parent reply other threads:[~2008-07-20 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 15:56 [PATCH] x86-kernel: declare some functions before they get used Jaswinder Singh
2008-07-14 15:58 ` Jaswinder Singh
2008-07-20 17:40 ` Ingo Molnar [this message]
2008-07-20 17:40 ` Ingo Molnar
2008-07-20 18:12 ` Jaswinder Singh
2008-07-20 18:24 ` Jaswinder Singh
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=20080720174018.GA16827@elte.hu \
--to=mingo@elte.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=jaswinder@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.