Greg KH had written, on 11/10/2010 06:11 PM, the following:
On Wed, Nov 10, 2010 at 02:38:10PM -0600, Nishanth Menon wrote:
[...]
diff --git a/linux-2.6-usb-bt-autosuspend.patch
b/linux-2.6-usb-bt-autosuspend.patch
index 68a0ecc..6235a97 100644
--- a/linux-2.6-usb-bt-autosuspend.patch
+++ b/linux-2.6-usb-bt-autosuspend.patch
@@ -1,3 +1,10 @@
+From: unknown Author <[email protected]>
+
+Subject: bluetooth: usb: enable autosuspend on probe
+
+Due to something
+
+Signed-off-by: unknown Author <[email protected]>
This doesn't make any sense, don't add "Signed-off-by:" with invalid
names.
And yes, I have complained before about patches in the meego tree with
no authorship or other information, nice to see someone try to follow up
with it, but the real person to solve it would be the one who originally
added it to the tree (hint, hint, hint...)
I agree - I unfortunately don't know who did the patch in the first
place - the hope is to have the owners ack their sourced patches so that
tracking the repo is easier :). my story started when I tried doing a
git am of the patches from kernel-dev to my private git repo[1] - these
would'nt apply as they were quilt patches incompatible with git am :( -
despite what we say in [2]
Ref:
[1] https://github.com/nmenon/linux-meego-panda/tree/meego-dev
[2]
http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors#Additional_Contribution_Guidelines
--
Regards,
Nishanth Menon
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
