From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 1/4] m68k: common PCI support definitions and code
Date: Fri, 29 Jun 2012 16:03:24 +1000 [thread overview]
Message-ID: <4FED452C.6060304@snapgear.com> (raw)
In-Reply-To: <CAMuHMdU-xTQAQ+fds6t_5rRwV7u3H_=37ePiOicQ=cNFgb=mjg@mail.gmail.com>
Hi Geert,
On 29/06/12 15:42, Geert Uytterhoeven wrote:
> On Fri, Jun 29, 2012 at 7:17 AM, <gerg@snapgear.com> wrote:
>> any m68k class CPU harwdare yet.
>
> hardware
Wow, you are quick :-) I'll fix that up.
Thanks for the feedback, and the acks!
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2012-06-29 6:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 5:17 [PATCH 0/4] m68k: ColdFire PCI bus support gerg
2012-06-29 5:17 ` [PATCH 1/4] m68k: common PCI support definitions and code gerg
2012-06-29 5:42 ` Geert Uytterhoeven
2012-06-29 6:03 ` Greg Ungerer [this message]
2012-06-29 5:45 ` Geert Uytterhoeven
2012-06-29 5:17 ` [PATCH 2/4] m68k: add PCI bus support for the ColdFire M54xx SoC family gerg
2012-06-29 5:17 ` [PATCH 3/4] m68k: add IO access definitions to support PCI on ColdFire platforms gerg
2012-06-29 5:46 ` Geert Uytterhoeven
2012-06-29 5:17 ` [PATCH 4/4] m68k: allow PCI bus to be enabled for ColdFire m54xx CPUs gerg
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=4FED452C.6060304@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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