linux-kernel - Re: [PATCH 0/2] MUSB: 2 patches to fix some bug found on Blackfin

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]

Message-Id: <200805211304.53082.david-b@pacbell.net>
Date:	Wed, 21 May 2008 13:04:52 -0700
From:	David Brownell <david-b@...bell.net>
To:	Felipe Balbi <me@...ipebalbi.com>
Cc:	Tony Lindgren <tony@...mide.com>, Bryan Wu <cooloney@...nel.org>,
	linux-omap@...r.kernel.org, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] MUSB: 2 patches to fix some bug found on Blackfin

On Wednesday 21 May 2008, Felipe Balbi wrote:
> 
> > I'm all for getting the musb_hdrc driver into the 2.6.27 queue...
> > I presume there are still some infrastructure changes in usbcore
> > that block that merge?  It'd be nice if we could merge musb_hdrc
> > without those changes (OTG related) and then update that stuff
> > separately.
> 
> Ok then, I'll prepare the patches during the next week and post
> here on l-o so people can comment.

When it's a USB patch, please post to linux-usb.  Most of the
relevant reviewers won't be on Linux-OMAP.  ;)

That said, I'm looking forward to seeing the www.beagleboard.org
hardware [1] become more generally available.  That will make some
musb_hdrc hardware available in a more developer-friendly rig than,
say, an N810 tablet.  And it might well get more folk in a position
where they can use that driver!  (I think some Blackfin devboards
are available already, but they're more pricey.)

- Dave

[1] http://www.elinux.org/BeagleBoard
--
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/