From: Philippe De Muyter <phdm@macqel.be>
To: Greg Ungerer <gerg@snapgear.com>
Cc: 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: Tue, 12 Jun 2012 09:26:19 +0200 [thread overview]
Message-ID: <20120612072619.GA17645@frolo.macqel> (raw)
In-Reply-To: <4FD6A8A8.1070809@snapgear.com>
Hi Greg,
On Tue, Jun 12, 2012 at 12:25:44PM +1000, Greg Ungerer wrote:
> Hi Philippe,
>
> 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 :)
Philippe
next prev parent reply other threads:[~2012-06-12 7:26 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 [this message]
2012-06-12 20:27 ` Geert Uytterhoeven
2012-06-13 0:27 ` 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=20120612072619.GA17645@frolo.macqel \
--to=phdm@macqel.be \
--cc=gerg@snapgear.com \
--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