From: pawelo@king.net.pl (Paul Osmialowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] arm: select different compiler flags for ARM CortexM3
Date: Wed, 24 Jun 2015 06:22:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1506240614540.24366@localhost.localdomain> (raw)
In-Reply-To: <20150623214818.GF7557@n2100.arm.linux.org.uk>
Hi Russell,
Thanks for the input. Seems like I trusted get_maintainer.pl blindly and
wasn't selective - it resulted in recipient list much too long.
As for this patch, I think I went too far with adding it. The board boots
without it properly, and since it covers more general Cortex-M related
problems I guess it should be excluded from next iteration of the whole
patchset.
The problems it adresses may still required further discussion, but I
think it should not block the whole thing.
On Tue, 23 Jun 2015, Russell King - ARM Linux wrote:
> On Tue, Jun 23, 2015 at 11:19:39PM +0200, Paul Osmialowski wrote:
>> This one is inspired by two commits published on Emcraft git repo:
>>
>> https://github.com/EmcraftSystems/linux-emcraft.git
>>
>> 1) 6302b692f570ff9d5645a6e72c11f87b0c1aa409
>> RT #62654. Fixed kernel crashes while running httpd by enabling
>> "-mfix-cortex-m3-ldrd" compiler option, which prevents compiler from
>> generating code like 'ldrd Ra, Rb, [Ra, #Imm]' - according to the 602117
>> Cortex-M3 Errata it may result in incorrect base register when interrupted
>> or faulted.
>>
>> by: Yuri Tikhonov <yur@emcraft.com>
>>
>> 2) 359d3cda84c01c0f3fae1a519b97a31f318f57ab
>> RT #62654. Removed "--march=..." leaving only "-mcpu=cortex-m3" to make
>> sure only the correct instructions will be generated.
>>
>> by: Sergei Poselenov <sposelenov@emcraft.com>
>>
>> I reworked these patches to make them less intrusive.
>>
>> Signed-off-by: Paul Osmialowski <pawelo@king.net.pl>
>
> NAK.
>
> The EFM32 code already added core support for Cortex-M3 cores, under
> the symbol CPU_V7M. Rather than implementing a whole new set of
> Cortex-M3 support alongside the existing code, please work with the
> EFM32 maintainer (Uwe Kleine-K?nig) to come up with a common set of
> core changes that you can all agree on for Cortex-M3.
>
> Please also try to be a little smarter with whom you're sending your
> patches to, the Cc list looks to be excessively long - having soo many
> recipients on your message is a good way to get your message rejected
> by mailing lists as spam.
>
> --
> FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
> according to speedtest.net.
>
next prev parent reply other threads:[~2015-06-24 4:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435094387-20146-1-git-send-email-pawelo@king.net.pl>
[not found] ` <1435094387-20146-2-git-send-email-pawelo@king.net.pl>
2015-06-23 21:48 ` [PATCH 1/9] arm: select different compiler flags for ARM CortexM3 Russell King - ARM Linux
2015-06-24 4:22 ` Paul Osmialowski [this message]
[not found] ` <1435094387-20146-4-git-send-email-pawelo@king.net.pl>
2015-06-23 21:51 ` [PATCH 3/9] arm: add call to CPU idle quirks handler Russell King - ARM Linux
[not found] ` <1435094387-20146-8-git-send-email-pawelo@king.net.pl>
2015-07-14 8:53 ` [PATCH 7/9] arm: twr-k70f120m: IOMUX driver for Kinetis SoC Linus Walleij
2015-09-08 8:04 ` Paul Osmialowski
2015-09-08 14:28 ` Linus Walleij
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=alpine.LNX.2.00.1506240614540.24366@localhost.localdomain \
--to=pawelo@king.net.pl \
--cc=linux-arm-kernel@lists.infradead.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