From: Randy Dunlap <rdunlap@xenotime.net>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, ak@suse.de
Subject: Re: [PATCH] Move functions declarations to header file
Date: Thu, 21 Jun 2007 08:41:01 -0700 [thread overview]
Message-ID: <20070621084101.73254fe7.rdunlap@xenotime.net> (raw)
In-Reply-To: <20070621145411.GA26091@redhat.com>
On Thu, 21 Jun 2007 11:54:11 -0300 Glauber de Oliveira Costa wrote:
> Some interrupt entry points are currently defined in i8259.c
> They probably belong in a header. Right now, their only user is
> init_IRQ, justifying their declaration in-file. But when virtualization
> comes in, we may be interested in using that functions in late
> initializations.
>
> Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
Patch is OK with me, but please insert patches inline in emails.
Lots of people who use mutt do this, so it must work and is the
preferred way.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-06-21 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 14:54 Glauber de Oliveira Costa
2007-06-21 15:41 ` Randy Dunlap [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=20070621084101.73254fe7.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gcosta@redhat.com \
--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®