From: Chanwoo Choi <cw00.choi@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
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>,
cwchoi00@gmail.com
Subject: Re: [GIT PULL] extcon for 3.8-rc4
Date: Wed, 16 Jan 2013 16:12:45 +0900 [thread overview]
Message-ID: <50F652ED.9020701@samsung.com> (raw)
In-Reply-To: <20130116064640.GB6087@kroah.com>
On 01/16/2013 03:46 PM, Greg KH wrote:
> On Wed, Jan 16, 2013 at 12:38:35PM +0900, Chanwoo Choi wrote:
>>>> 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?
>>>
>> I understand and thanks for your comment. I will resend only one pull-request for
>> extcon to include it for -next branch. I don't send separate pull-request
>> for bugfixes patch.
>
> Why not send a bugfix pull request? Are none of these for 3.8? If so,
> fine, but be sure to go through them to determine this.
I think that it isn't critical bug and relevant to extcon core driver.
And The issue is trivial and depend on new feature of max77693 extcon driver.
Thank you,
Chanwoo Choi
prev parent reply other threads:[~2013-01-16 7:12 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
2013-01-16 3:38 ` Chanwoo Choi
2013-01-16 6:46 ` Greg KH
2013-01-16 7:12 ` Chanwoo Choi [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=50F652ED.9020701@samsung.com \
--to=cw00.choi@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cwchoi00@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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