From: Ralf Baechle <ralf@linux-mips.org>
To: John Crispin <blogic@openwrt.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/4] MIPS: lantiq: move IRQ_RES macro to a headerfile
Date: Tue, 10 May 2011 15:23:59 +0100 [thread overview]
Message-ID: <20110510142359.GA15184@linux-mips.org> (raw)
In-Reply-To: <1304959750-8557-2-git-send-email-blogic@openwrt.org>
As discussed folded into the existing series in linux-queue. Could you
please check if the result is making sense?
Thanks,
Ralf
next prev parent reply other threads:[~2011-05-10 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1304959750-8557-1-git-send-email-blogic@openwrt.org>
2011-05-09 16:49 ` [PATCH 1/4] MIPS: lantiq: move IRQ_RES macro to a headerfile John Crispin
2011-05-10 14:23 ` Ralf Baechle [this message]
2011-05-09 16:49 ` [PATCH 2/4] MIPS: lantiq: adds Amazon SE serial port platform device John Crispin
2011-05-10 14:24 ` Ralf Baechle
2011-05-09 16:49 ` [PATCH 3/4] MIPS: lantiq: cleanup machine specific files John Crispin
2011-05-10 14:24 ` Ralf Baechle
2011-05-09 16:49 ` [PATCH 4/4] MIPS: lantiq: add a soc specific setup function John Crispin
2011-05-10 14:24 ` Ralf Baechle
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=20110510142359.GA15184@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.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