linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Philippe De Muyter <phdm@macqel.be>,
	linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68knommu: allow ColdFire CPUs to use unaligned accesses
Date: Wed, 13 Jun 2012 10:27:45 +1000	[thread overview]
Message-ID: <4FD7DE81.8080407@snapgear.com> (raw)
In-Reply-To: <CAMuHMdVViTNCfWKPt9_pmaqEmjcuAT=sfz-vhUCNHiGKAm=p3g@mail.gmail.com>

On 13/06/12 06:27, Geert Uytterhoeven wrote:
> On Tue, Jun 12, 2012 at 9:26 AM, Philippe De Muyter<phdm@macqel.be>  wrote:
>> On Tue, Jun 12, 2012 at 12:25:44PM +1000, Greg Ungerer wrote:
>>> On 08/06/12 23:35, Philippe De Muyter wrote:
>> ...
>>>>
>>>> I mentionned that only to make you able to soften the commit comment :)
>>>
>>> Ok, makes sense. I should probably have mentioned that this means
>>> the ColdFire processors currently support by Linux :-)
>>>
>>> Something like:
>>>
>>> á All of the current Linux supported ColdFire CPUs handle unaligned
>>> á memory accesses. So remove the CONFIG_CPU_HAS_NO_UNALIGNED option
>>> á selection for ColdFire. If we ever support a specific ColdFire CPU
>>> á that does not support unaligned accesses then we can insert the
>>> á CONFIG_CPU_HAS_NO_UNALIGNED for that specific CPU type.
>>
>> That's perfect. áThe line about dumb copying of the m68knommu settings
>> was too much self-flagellation for you to my eyes :)
>
> So I rewrote history on my for-3.6 branch...

Thanks Geert!

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

      reply	other threads:[~2012-06-13  0:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  5:43 [PATCH] m68knommu: allow ColdFire CPUs to use unaligned accesses gerg
2012-06-08  7:19 ` Geert Uytterhoeven
2012-06-08  9:10   ` Greg Ungerer
2012-06-08 10:39 ` Philippe De Muyter
2012-06-08 12:19   ` Greg Ungerer
2012-06-08 13:35     ` Philippe De Muyter
2012-06-12  2:25       ` Greg Ungerer
2012-06-12  7:26         ` Philippe De Muyter
2012-06-12 20:27           ` Geert Uytterhoeven
2012-06-13  0:27             ` Greg Ungerer [this message]

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=4FD7DE81.8080407@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=phdm@macqel.be \
    --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;
as well as URLs for NNTP newsgroup(s).