linux-kernel - Re: linux-next: manual merge of the usb tree with Linus' tree

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] [day] [month] [year] [list]

Message-ID: <20130125205209.GA8950@kroah.com>
Date:	Fri, 25 Jan 2013 12:52:09 -0800
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Wolfgang Frisch <wfpub@...mbden.net>,
	Johan Hovold <jhovold@...il.com>
Subject: Re: linux-next: manual merge of the usb tree with Linus' tree

On Mon, Jan 21, 2013 at 01:02:19PM -0800, Greg KH wrote:
> On Mon, Jan 21, 2013 at 03:07:11PM +1100, Stephen Rothwell wrote:
> > Hi Greg,
> > 
> > Today's linux-next merge of the usb tree got a conflict in
> > drivers/usb/serial/io_ti.c between commit 1ee0a224bc9a ("USB: io_ti: Fix
> > NULL dereference in chase_port()") from Linus' tree and commit
> > f40d781554ef ("USB: io_ti: kill custom closing_wait implementation") from
> > the usb tree.
> > 
> > I fixed it up (the latter removed the code fixed by the former, so I just
> > used thet) and can carry the fix as necessary (no action is required).
> 
> Yes, that is the correct fix, thanks for this.

This should now be resolved in my trees.

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/