linux-kernel - Re: [PATCH 0/3] usbip: move usbip out of staging

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAKocOONNKZXHS1+ZDrMRu4noOCi+OmSVvhcxBrH+iNDyB1B7zw@mail.gmail.com>
Date:	Thu, 7 Aug 2014 13:48:53 -0600
From:	Shuah Khan <shuahkhan@...il.com>
To:	Valentina Manea <valentina.manea.m@...il.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Tülin İzer <tulinizer@...il.com>,
	Alan Stern <stern@...land.harvard.edu>, mail@...ermatthias.de,
	hdegoede@...hat.com, Federico Manzan <f.manzan@...il.com>,
	Kurt Garloff <kurt@...loff.de>, linux-usb@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	"Linux Kernel Community @ ROSEdu" <firefly@...ts.rosedu.org>,
	Andy Grover <andy.grover@...il.com>, max@...eler.com
Subject: Re: [PATCH 0/3] usbip: move usbip out of staging

On Thu, Aug 7, 2014 at 1:36 PM, Valentina Manea
<valentina.manea.m@...il.com> wrote:
> On Wed, Aug 6, 2014 at 10:33 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
>> On Thu, Aug 07, 2014 at 08:10:25AM +0300, Valentina Manea wrote:
>>> This is a resend of the patch series from March.
>>>
>>> After migrating userspace code to libudev, converting usbip-host
>>> to a device driver and various bug fixes and enhancements, USB/IP
>>> is fully functional and can be moved out of staging.
>>>
>>> This patch series moves it as following:
>>> * userspace code to tools/usb/usbip
>>> * kernel code to drivers/usb/usbip
>>>
>>> Besides this, a warning generated in the kernel code is solved.
>>
>> What kernel version is this against?
>>
>
> I rebased my tree against master in the staging tree.
>
>> And can we get a maintainer for this code?  I don't want to see it sit
>> "ownerless" in the kernel tree.  Will you be willing to do this?
>>
>
> Yes. But I should be briefed about that responsibilities will this involve.
>

If you would like a back-up, I can volunteer to be co-maintainer for this
driver.

-- Shuah
--
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/