From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: gerg@uclinux.org, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] m68knommu: change definitions of __pa() and __va()
Date: Tue, 12 Jan 2010 10:25:41 +1000 [thread overview]
Message-ID: <4B4BC185.1030509@snapgear.com> (raw)
In-Reply-To: <10f740e81001110744n5aaf6b4ay1afe28671f20e2c5@mail.gmail.com>
Hi Geert,
Geert Uytterhoeven wrote:
> On Mon, Jan 11, 2010 at 06:02, Greg Ungerer <gerg@snapgear.com> wrote:
>> I would like to submit this to Linus ASAP, to fix broken compilation
>> in 2.6.33-rc3 for m68knommu targets. It effects m68k includes, so I
>> wanted to get some review here first.
>
> The m68kmmu part looks fine to me.
Thanks, I'll send it to Linus now.
Regards
Greg
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
--
------------------------------------------------------------------------
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:[~2010-01-12 0:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 5:02 [PATCH] m68knommu: change definitions of __pa() and __va() Greg Ungerer
2010-01-11 15:44 ` Geert Uytterhoeven
2010-01-12 0:25 ` Greg Ungerer [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-12 0:39 Greg Ungerer
2010-01-12 0:39 ` Greg Ungerer
2010-01-12 0:53 ` Linus Torvalds
2010-01-12 7:02 ` Greg Ungerer
2010-01-12 9:45 ` Greg Ungerer
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=4B4BC185.1030509@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.