From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH 00/12] m68knommu: generalize the ColdFire clock support for all CPU types
Date: Fri, 16 Nov 2012 19:09:14 +1000 [thread overview]
Message-ID: <50A602BA.8060500@snapgear.com> (raw)
In-Reply-To: <CAMuHMdVLF+aqWWAG3_O6bzjaOGRyzSgSQqmddDwAh6coKaNPVA@mail.gmail.com>
Hi Geert,
On 11/16/2012 04:28 PM, Geert Uytterhoeven wrote:
> On Fri, Nov 16, 2012 at 5:47 AM, <gerg@snapgear.com> wrote:
>> ColdFire p[eripheraps, instead of hard coded clock definitions.
>
> peripherals
Thanks for the fixups. All applied.
Regards
Greg
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
next prev parent reply other threads:[~2012-11-16 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 4:47 [PATCH 00/12] m68knommu: generalize the ColdFire clock support for all CPU types gerg
2012-11-16 4:47 ` [PATCH 01/12] m68knommu: add clock creation support macro for other ColdFire CPUs gerg
2012-11-16 6:30 ` Geert Uytterhoeven
2012-11-16 4:47 ` [PATCH 02/12] m68knommu: add clock definitions for 5206 ColdFire CPU types gerg
2012-11-16 4:47 ` [PATCH 03/12] m68knommu: add clock definitions for 523x " gerg
2012-11-16 4:47 ` [PATCH 04/12] m68knommu: add clock definitions for 5249 " gerg
2012-11-16 4:47 ` [PATCH 05/12] m68knommu: add clock definitions for 525x " gerg
2012-11-16 4:47 ` [PATCH 06/12] m68knommu: add clock definitions for 5272 " gerg
2012-11-16 4:47 ` [PATCH 07/12] m68knommu: add clock definitions for 527x " gerg
2012-11-16 4:47 ` [PATCH 08/12] m68knommu: add clock definitions for 528x " gerg
2012-11-16 4:47 ` [PATCH 09/12] m68knommu: add clock definitions for 5307 " gerg
2012-11-16 4:47 ` [PATCH 10/12] m68knommu: add clock definitions for 5407 " gerg
2012-11-16 4:47 ` [PATCH 11/12] m68knommu: add clock definitions for 54xx " gerg
2012-11-16 4:47 ` [PATCH 12/12] m68knommu: modify clock code so it can be used by all " gerg
2012-11-16 6:28 ` [PATCH 00/12] m68knommu: generalize the ColdFire clock support for all " Geert Uytterhoeven
2012-11-16 9:09 ` Greg Ungerer [this message]
2012-11-26 15:34 ` [uClinux-dev] " Thomas Petazzoni
2012-11-26 22:49 ` 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=50A602BA.8060500@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.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