From: Greg KH <gregkh@linuxfoundation.org>
To: cw00.choi@samsung.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [GIT PULL] extcon for 3.8-rc4
Date: Tue, 15 Jan 2013 05:49:41 -0800 [thread overview]
Message-ID: <20130115134941.GA25473@kroah.com> (raw)
In-Reply-To: <CAGTfZH27VUuqqx5b4trMSDDDceWqwHE2wqPZdLbWvvBvbrzpKg@mail.gmail.com>
On Tue, Jan 15, 2013 at 10:23:44PM +0900, Chanwoo Choi wrote:
> On Tuesday, January 15, 2013, Greg KH wrote:
>
> On Tue, Jan 15, 2013 at 09:09:20PM +0900, Chanwoo Choi wrote:
> > On Tuesday, January 15, 2013, Greg KH wrote:
> >
> > On Tue, Jan 15, 2013 at 04:34:18PM +0900, Chanwoo Choi wrote:
> > > Hi Greg,
> > >
> > > This is the extcon pull request for Linux 3.8-rc4.
> > >
> > > Please pull extcon with following updates:
> > >
> > > Update to max77693/max8997 extcon driver:
> > > - Using MHL_TA cable for charging.
> > > - Support JIG cable.
> > > - Support Dock-Audio device for playing music and button of device.
> > > - Support Dock-Smart device for desktop mode with mouse/keyboard.
> > > - Set default UART/USB path on probe().
> > > - Check the state/type of cable after completing initialization.
> > > - Code clean to remove duplicate code and bug fix related to
> sequence of
> > interrupt.
> > > - Fix irq_flag of max8997/max77693 driver.
> > >
> > > Update to arizona extcon driver:
> > > - Headphone measurements.
> > > - Alternative detection mechanism for non-default system designs.
> > > - Microphone clamp integration.
> > > - Support for additional detection pin.
> > > - MICBIAS rise time configuration.
> > >
> > > Thanks in advance for pulling,
> >
> > This request is for inclusion in 3.9, right? This seems much too big
> > for 3.8 at the moment.
> >
> >
> > If you think that, I agree your opinion about including this request in
> 3.9.
>
> That's really up to you, as a subsystem maintainer, to decide about.
> You need to take bugfixes and ask for them to be included in the 3.8,
> and new features and other work, for 3.9.
>
> OK, I will resend pull-request to include only bugfixes patch in 3.8.
> After released v3.8-rc7 or 3.8-rc8 kernel, I will send pull-request of extcon
> to include new feature patches of extcon driver in 3.9.
No, you can send me that pull request now as well, I have two different
branches, one to go to Linus for this release, and one for the next one.
Both of them show up in linux-next. You should have the same.
So you can send me two pull requests now, does that make more sense?
thanks,
greg k-h
next prev parent reply other threads:[~2013-01-15 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 7:34 [GIT PULL] extcon for 3.8-rc4 Chanwoo Choi
2013-01-15 11:37 ` Greg KH
[not found] ` <CAGTfZH2r9TaNEPQ5am-UFwQd9t_qegxfo3MMOwJxvfctid7=-Q@mail.gmail.com>
2013-01-15 12:13 ` Greg KH
2013-01-15 12:15 ` Mark Brown
[not found] ` <CAGTfZH27VUuqqx5b4trMSDDDceWqwHE2wqPZdLbWvvBvbrzpKg@mail.gmail.com>
2013-01-15 13:49 ` Greg KH [this message]
2013-01-16 3:38 ` Chanwoo Choi
2013-01-16 6:46 ` Greg KH
2013-01-16 7:12 ` Chanwoo Choi
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=20130115134941.GA25473@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox