From: john.stultz@linaro.org (John Stultz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 0/4] ARM: KDB FIQ debugger
Date: Wed, 14 Nov 2012 17:45:31 -0800 [thread overview]
Message-ID: <50A4493B.3020207@linaro.org> (raw)
In-Reply-To: <20121016003756.GA23146@lizard>
On 10/15/2012 05:37 PM, Anton Vorontsov wrote:
> Hello Russell,
>
> The KDB/NMI core support has been merged into v3.7-rc1, so the only ARM
> bits are pending now. I believe I addressed all your previous comments,
> but surely there might be something else to improve, thus would be great
> if you could take a look at this.
>
> The patches were rebased onto v3.7-rc1, and this is the only change in
> v10.
>
> Old changelogs and rationale for these patches can be found here:
>
> v1-v5, rationale: http://lkml.org/lkml/2012/9/10/2
> v6: http://lkml.org/lkml/2012/9/10/2
> v7: http://lkml.org/lkml/2012/9/13/367
> v8: http://lkml.org/lkml/2012/9/19/525
> v9: http://lkml.org/lkml/2012/9/24/538
Just catching up from being on leave, but I've not seen any response to
this.
Are there objections to this patch set? Or did it just get buried in
everyone's inbox?
thanks
-john
prev parent reply other threads:[~2012-11-15 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 0:37 [PATCH v10 0/4] ARM: KDB FIQ debugger Anton Vorontsov
2012-10-16 0:39 ` [PATCH 1/4] ARM: Move some macros from entry-armv to entry-header Anton Vorontsov
2012-10-16 0:39 ` [PATCH 2/4] ARM: Add KGDB/KDB FIQ debugger generic code Anton Vorontsov
2012-10-16 0:39 ` [PATCH 3/4] ARM: VIC: Add a couple of low-level FIQ management helpers Anton Vorontsov
2012-10-16 0:39 ` [PATCH 4/4] ARM: versatile: Make able to use UART ports for KGDB FIQ debugger Anton Vorontsov
2012-11-15 1:45 ` John Stultz [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=50A4493B.3020207@linaro.org \
--to=john.stultz@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).