public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ARM: OMAP: clock: convert AM3517/3505 detection/flags to AM35xx
Date: Mon, 30 Apr 2012 17:18:57 -0700	[thread overview]
Message-ID: <878vhckb2m.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204301746040.10308@utopia.booyaka.com> (Paul Walmsley's message of "Mon, 30 Apr 2012 17:46:28 -0600 (MDT)")

Paul Walmsley <paul@pwsan.com> writes:

> On Mon, 30 Apr 2012, Kevin Hilman wrote:
>
>> From: Paul Walmsley <paul@pwsan.com>
>
> Looks good to me but I think you created this patch, right? :-)

er, yeah.

Seems the combined version I pulled from your temporary branch had your
authorship (maybe because of the combine?) and I didn't notice.  

Anyways, feel free free to fix up.

Thanks,

Kevin



  reply	other threads:[~2012-05-01  0:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 23:30 [PATCH 0/3] ARM: OMAP3: clock: cleanup AM35xx clock flags Kevin Hilman
2012-04-30 23:30 ` [PATCH 1/3] ARM: OMAP3: clock data: replace 3503/3517 flag with AM35x flag for UART4 Kevin Hilman
2012-04-30 23:30 ` [PATCH 2/3] ARM: OMAP3: clock data: treat all AM35x devices the same Kevin Hilman
2012-04-30 23:30 ` [PATCH 3/3] ARM: OMAP: clock: convert AM3517/3505 detection/flags to AM35xx Kevin Hilman
2012-04-30 23:46   ` Paul Walmsley
2012-05-01  0:18     ` Kevin Hilman [this message]
2012-05-01  2:17       ` Paul Walmsley
2012-05-02  8:24 ` [PATCH 0/3] ARM: OMAP3: clock: cleanup AM35xx clock flags Paul Walmsley

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=878vhckb2m.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    /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