From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/3] Updated Cortex-M3 series
Date: Tue, 25 Sep 2012 17:00:26 +0200 [thread overview]
Message-ID: <20120925150026.GG21730@pengutronix.de> (raw)
In-Reply-To: <5061C3FE.7050400@arm.com>
Hello,
On Tue, Sep 25, 2012 at 03:47:26PM +0100, Jonathan Austin wrote:
> On 21/09/12 20:00, Uwe Kleine-K?nig wrote:
> > On Thu, Aug 16, 2012 at 10:29:32PM +0200, Uwe Kleine-K?nig wrote:
> >> On Fri, Aug 03, 2012 at 12:10:11PM +0200, Uwe Kleine-K?nig wrote:
> >>> the only changes compared to v5 (sent starting with Message-id:
> >>> 1341512035-8173-1-git-send-email-u.kleine-koenig at pengutronix.de)
> >>> are that several debug pr_infos were dropped that I missed to remove
> >>> before. Thanks to Will Deacon for pointing out that problem.
> >>> Furthermore I rebased (trivially) to v3.5.
> >> Any feedback from your side? It would be great to get this in for 3.7
> >> with some time in next before.
> > What must happen to get some feed back? Is it worth to assert the stuff
> > still works with 3.6-rc6?
>
> I hope to have a chance to look at these towards the end of the week...
>
> Looking at the patch series at a very superficial level, I wonder why
> you've chosen not to include any Kconfig/NVIC support at this stage,
> especially as you've posted some before and there appears to be
> something (presumably) working in your efm32 branch...
>
> It would be a shame to spend time on merging the basic support if there
> are issues that mean the interrupt support won't follow.
I plan to expand common/gic.c for interrupt support. Currently I don't
do much though because getting feedback and the changes into mainline is
quite hard and I don't want to spend time now and hear later that I did
it wrong or something. So I put my efforts on hold and only ping from
time to time. :-(
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2012-09-25 15:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 10:10 [PATCH v6 0/3] Updated Cortex-M3 series Uwe Kleine-König
2012-08-03 10:10 ` [PATCH v6 1/3] ARM: make cr_alignment read-only #ifndef CONFIG_CPU_CP15 Uwe Kleine-König
2012-08-03 10:10 ` [PATCH v6 2/3] Cortex-M3: Add base support for Cortex-M3 Uwe Kleine-König
2012-08-03 10:10 ` [PATCH v6 3/3] Cortex-M3: Add support for exception handling Uwe Kleine-König
2012-08-03 14:07 ` [PATCH v6 0/3] Updated Cortex-M3 series Arnd Bergmann
2012-08-03 14:50 ` Uwe Kleine-König
2012-08-03 15:17 ` Shiraz Hashim
2012-08-04 13:57 ` Uwe Kleine-König
2012-08-03 15:37 ` Jonathan Austin
2012-08-16 20:29 ` Uwe Kleine-König
2012-09-21 19:00 ` Uwe Kleine-König
2012-09-25 14:47 ` Jonathan Austin
2012-09-25 15:00 ` Uwe Kleine-König [this message]
2012-09-26 18:03 ` Will Deacon
2012-09-26 19:27 ` Uwe Kleine-König
2012-10-17 8:14 ` Uwe Kleine-König
2012-10-08 15:43 ` new branch for linux-next [Was: [PATCH v6 0/3] Updated Cortex-M3 series] Uwe Kleine-König
2012-10-08 15:47 ` Russell King - ARM Linux
2012-10-11 22:51 ` Stephen Rothwell
2012-10-15 23:08 ` Stephen Rothwell
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=20120925150026.GG21730@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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 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.