linux-kernel - Re: [GIT PULL] extcon for 3.8-rc4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Jan 2013 22:46:40 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Chanwoo Choi <cw00.choi@...sung.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"myungjoo.ham@...sung.com" <myungjoo.ham@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	cwchoi00@...il.com
Subject: Re: [GIT PULL] extcon for 3.8-rc4

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.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/