All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-kernel@vger.kernel.org,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [GIT PULL] extcon fixes for 3.9-rc6
Date: Sun, 7 Apr 2013 19:36:21 -0700	[thread overview]
Message-ID: <20130408023621.GA5894@kroah.com> (raw)
In-Reply-To: <51622526.8000302@samsung.com>

On Mon, Apr 08, 2013 at 11:02:14AM +0900, Chanwoo Choi wrote:
> Hi Greg,
> 
> This is extcon fixes for 3.9-rc6
> Please pull extcon with following updates.
> 
> Best Regards and thanks,
> Chanwoo Choi
> 
> The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
> 
>   Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-3.9-rc6
> 
> for you to fetch changes up to 2fbeb4347e02078828510e5fe43ab4bea21b20d1:
> 
>   extcon: max8997: Fix return value (2013-04-08 09:13:18 +0900)
> 
> ----------------------------------------------------------------
> This is small fixes for extcon driver.
> 
> MAX77693 extcon driver
> - Add 'static' keryword to internal data structure
> - Fix return value using 'ret' instead of hardcoding
> 
> MAX8997 extcon driver
> - Use dev_err() instead of pr_err()
> - Fix return value using 'ret' instead of hardcoding

None of these should go into 3.9-final, they are all trivial cleanups.
Only major bug fixes or regressions should be sent right now for 3.9,
sorry.

I will be glad to pull these into my -next branch for 3.10 if you want.

greg k-h

  reply	other threads:[~2013-04-08  2:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  2:02 [GIT PULL] extcon fixes for 3.9-rc6 Chanwoo Choi
2013-04-08  2:36 ` Greg KH [this message]
2013-04-08  3:52   ` Chanwoo Choi
2013-04-08 18:33     ` Greg KH

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=20130408023621.GA5894@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.