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: <55935FC1.8090203@codeweavers.com>
Date:	Tue, 30 Jun 2015 22:34:25 -0500
From:	Jeremy White <jwhite@...eweavers.com>
To:	Greg KH <greg@...ah.com>
CC:	hdegoede@...hat.com, spice-devel@...ts.freedesktop.org,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/1] Add a usbredir kernel module to remotely connect
 USB devices over IP.

>
> It's pointless to post a patch that you know has problems with it (i.e.
> it's not even in proper kernel coding style), as it will never be
> reviewed or even looked at.

Thanks for the reply, and I'm sorry for the clumsy ask.

I would still appreciate feedback on two points:

   1.  Is the basic premise reasonable?  Is Hans correct in asserting 
that an alternate USB over IP module will be considered?

   2.  Do I correctly understand that there are no circumstances where 
copied code can be left unmodified?  Even in the case where the copied 
code is working, production code, and the changes would be just for style?

>
> Please do the most basic of polite things and fix this up before posting
> things.

It is often difficult for a newcomer to know what the polite thing is, 
even after studying FAQs and documentation.

I appreciate your patience (and clue bats) as I try to learn.

>
> And really, all in one patch?  That too is pretty hard to review...

Yeah.  I see the point of pain.  I did not see a solution as I formed 
the patch, but I'll try harder before resending.

Cheers,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ