From: Roman Zippel <zippel@linux-m68k.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: APUS irq patch
Date: Sun, 11 Nov 2001 12:54:25 +0100 [thread overview]
Message-ID: <3BEE66F1.C963E0A9@linux-m68k.org> (raw)
In-Reply-To: 20011110195803.C573@cpe-24-221-152-185.az.sprintbbd.net
Hi,
Tom Rini wrote:
> Looks good, applied. In the future can you please make the patches vs
> _devel?
I did, but I only didn't made them against the newest version.
bye, Roman
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-11 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 22:10 APUS irq patch Roman Zippel
2001-11-11 2:58 ` Tom Rini
2001-11-11 11:54 ` Roman Zippel [this message]
2001-11-11 16:18 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 23:18 Roman Zippel
2001-11-01 23:53 ` Tom Rini
2001-11-02 0:27 ` Roman Zippel
2001-11-02 0:57 ` Tom Rini
2001-11-02 9:59 ` Roman Zippel
2001-11-02 16:03 ` Tom Rini
2001-11-02 21:54 ` Paul Mackerras
2001-11-02 22:44 ` Roman Zippel
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=3BEE66F1.C963E0A9@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).