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  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:	Sat, 9 Aug 2014 07:17:16 -0700
From:	Greg KH <>
To:	Valentina Manea <>
Cc:	Tülin İzer <>,
	Alan Stern <>,,, Federico Manzan <>,
	Kurt Garloff <>,,,
	"Linux Kernel Community @ ROSEdu" <>,
	Andy Grover <>,
Subject: Re: [PATCH 0/3] usbip: move usbip out of staging

On Fri, Aug 08, 2014 at 09:41:48PM -0700, Valentina Manea wrote:
> On Thu, Aug 7, 2014 at 1:16 PM, Greg KH <> wrote:
> >
> > The top of the MAINTAINERS should have this information, look in the S:
> > Status section about what type of category you are in.
> >
> > Basically I'd like you to be the one to handle patches that are sent in
> > for the code, just by reviewing them, you don't have to send them on to
> > me if you don't want to (some usb subsystem maintainers do do this, like
> > for usb-serial and xhci), it's up to you.
> >
> > Also, any bug reports or questions about the code would come to you
> > first, along with the rest of the linux-usb@...r developers, you aren't
> > alone in this at all.
> >
> Ok, this sounds good. I suppose sending you the patches involves
> picking them up from the email, batching them and sending with
> send-email.

Yes, that would be ideal, but you don't have to do that if you don't
want to.  A simple "Acked-by:" line added to an email that you cc: me on
with the patch should suffice if that is easier (it's how other
developers do it to let me know they have reviewed it.)

Which ever works best / easiest for you.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists