linux-kernel - Re: linux-next: Tree for Apr 20 (usb & target)

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: <20120504221534.GA16430@kroah.com>
Date:	Fri, 4 May 2012 15:15:34 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
Cc:	balbi@...com, Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Randy Dunlap <rdunlap@...otime.net>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org, target-devel@...r.kernel.org
Subject: Re: linux-next: Tree for Apr 20 (usb & target)

On Fri, May 04, 2012 at 09:56:39AM -0700, Nicholas A. Bellinger wrote:
> On Fri, 2012-05-04 at 12:41 +0300, Felipe Balbi wrote:
> > Hi,
> > 
> 
> <SNIP>
> 
> > > 
> > > After the recommended change, the in-kernel config using a single gadget
> > > driver (the target) are able to build.  Thanks for the detailed
> > > explanation btw.. ;)
> > > 
> > > I've made the same change for tcm_usb_gadget in lio-core, and updated
> > > for-next-merge with the following merge patch:
> > > 
> > > http://git.kernel.org/?p=linux/kernel/git/nab/target-pending.git;a=commit;h=0c41520201bc0933d65b8644173802778f426234
> > > 
> > > Please let me know if you have any other changes that should go into
> > > sunday's linux-next build.
> > 
> > It looks ok to me. You can add my Acked-by: Felipe Balbi <balbi@...com>
> > 
> 
> Thanks Felipe!
> 
> So with your Ack in place and if there are no more objections, the plan
> is now to take tcm_usb_gadget through target-pending/for-next-merge
> (along with sbp-target) for an initial upstream merge.
> 
> Also, I'm fine if USB folks would prefer to take this via their tree
> now that the gadget target is residing within drivers/usb/gadget/, but
> AFAICT this looks harmless enough to merge directly via the target tree.

That's fine with me as well.

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/