linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sangbeom Kim <sbkim73@samsung.com>
To: "'Mark Brown'" <broonie@opensource.wolfsonmicro.com>
Cc: "'Liam Girdwood'" <lrg@ti.com>,
	sameo@linux.intel.com, linux-kernel@vger.kernel.org,
	sbkim01@gmail.com
Subject: RE: [PATCH V2 3/7] regulator: s5m8767: Modify function and variable name
Date: Tue, 10 Jul 2012 11:11:41 +0900	[thread overview]
Message-ID: <008601cd5e41$586bfe10$0943fa30$@com> (raw)
In-Reply-To: <20120709130309.GD3934@opensource.wolfsonmicro.com>

Hi
Monday, July 09, 2012 10:03 PM +0900, Mark Brown wrote:

> This needs to be squashed down into the patch doing the rename in the
> core to avoid build breakage.  Otherwise looks good.
Ok, I will squash and resend it.

Thanks,
Sangbeom.



      reply	other threads:[~2012-07-10  2:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-07  9:39 [PATCH V2 3/7] regulator: s5m8767: Modify function and variable name Sangbeom Kim
2012-07-09 13:03 ` Mark Brown
2012-07-10  2:11   ` Sangbeom Kim [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='008601cd5e41$586bfe10$0943fa30$@com' \
    --to=sbkim73@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=sbkim01@gmail.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;
as well as URLs for NNTP newsgroup(s).