public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@deeprootsystems•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] Allow late mdesc detection, v4
Date: Mon, 30 Aug 2010 09:22:21 -0700	[thread overview]
Message-ID: <87iq2s8402.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1283141254.2798.1.camel@pororo> (Jeremy Kerr's message of "Mon, 30 Aug 2010 12:07:34 +0800")

Jeremy Kerr <jeremy.kerr@canonical•com> writes:

> Hi Kevin,
>
>> > As they have more complex and/or new debug macros, the following platforms
>> > could do with extra testing:
>> >  * omap (mach-omap1 and mach-omap2)
>> >  * davinci
>> 
>> Tested on a couple flavors of DaVinci SoCs, so for davinci
>> 
>
> Awesome, thank you for the testing.
>
>> Signed-off-by: Kevin Hilman <khilman@deeprootsystems•com>
>> 
>
> OK if I change this to Tested-by: ?

Sure, np

Kevin

  reply	other threads:[~2010-08-30 16:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23  8:50 [PATCH 0/3] Allow late mdesc detection, v4 Jeremy Kerr
2010-08-23  8:50 ` [PATCH 3/3] arm: use addruart macro to establish debug mappings Jeremy Kerr
2010-08-23  8:50 ` [PATCH 2/3] arm: return both physical and virtual addresses from addruart Jeremy Kerr
2010-08-23 10:05   ` Uwe Kleine-König
2010-08-23 14:36     ` Jeremy Kerr
2010-08-23  8:50 ` [PATCH 1/3] arm/debug: consolidate addruart macros for CONFIG_DEBUG_ICEDCC Jeremy Kerr
2010-08-27 18:21 ` [PATCH 0/3] Allow late mdesc detection, v4 Kevin Hilman
2010-08-30  4:07   ` Jeremy Kerr
2010-08-30 16:22     ` Kevin Hilman [this message]
2010-09-01  7:39 ` Russell King - ARM Linux
2010-10-15  3:42   ` Nicolas Pitre
2010-10-18 14:19     ` Russell King - ARM Linux
2010-10-18 14:32       ` Nicolas Pitre
2010-10-19  1:34         ` Tony Lindgren

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=87iq2s8402.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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