public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Chris Ball' <cjb@laptop.org>
Cc: 'Rajeshwari Shinde' <rajeshwari.s@samsung.com>,
	linux-mmc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH V6] SDHCI: S3C: Use generic clock names for sdhci bus clock options
Date: Thu, 03 Nov 2011 11:14:41 +0900	[thread overview]
Message-ID: <013501cc99ce$58ea8920$0abf9b60$%kim@samsung.com> (raw)
In-Reply-To: <m2aa8e9zn3.fsf@bob.laptop.org>

Chris Ball wrote:
> 
> Hi Kukjin,
> 
> On Wed, Nov 02 2011, Kukjin Kim wrote:
> >> This patch modifies the driver to stop depending on the clock names
> >> being passed from the platform and switch over to bus clock lookup
> >> using generic clock names.
> >>
> >> V6 Changes:
> >> Changed sprintf to snprintf as suggested by Chris Ball.
> >>
> >> Signed-off-by: Rajeshwari Shinde <rajeshwari.s@samsung.com>
> >
> > Acked-by: Kukjin Kim <kgene.kim@samsung.com>
> >
> > Hi Chirs,
> >
> > Could you please pick this up in your tree for this merge window?
> 
> Might be easier to have you send this, if you don't mind, since I'm
> still traveling and have already sent my main pull request.  Thanks!
> 
> Acked-by: Chris Ball <cjb@laptop.org>
> 
Hi Chris,

OK, I picked this up in my tree.
Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.


  reply	other threads:[~2011-11-03  2:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31  5:44 [PATCH V6] SDHCI: S3C: Use generic clock names for sdhci bus clock options Rajeshwari Shinde
2011-11-02 12:12 ` Kukjin Kim
2011-11-02 17:56   ` Chris Ball
2011-11-03  2:14     ` Kukjin Kim [this message]
2011-11-02 20:41 ` Thomas Abraham

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='013501cc99ce$58ea8920$0abf9b60$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=cjb@laptop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rajeshwari.s@samsung.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