From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH 2.5] More i8259 cleanups
Date: Wed, 15 May 2002 14:36:53 -0700 [thread overview]
Message-ID: <20020515213653.GA20456@opus.bloom.county> (raw)
In-Reply-To: <3CE2C88D.6010908@embeddededge.com>
On Wed, May 15, 2002 at 04:43:57PM -0400, Dan Malek wrote:
> Tom Rini wrote:
>
> >Hey all. I've been doing more OpenPIC/i8259 work and here's the next
> >patch I'll be pushing to linuxppc-2.5 soon.
>
> Looks good.....just one little thing, how about we wrap some more of these
> functions with __init attributes?
It's on my todo list. I'll probably do it in 2.4 first as well,
soonish.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-15 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 17:11 [PATCH 2.5] More i8259 cleanups Tom Rini
2002-05-15 20:43 ` Dan Malek
2002-05-15 21:36 ` Tom Rini [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=20020515213653.GA20456@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).