linux-kernel - Re: [PATCH 0/2] small xhci cleanups

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]

Date:	Tue, 9 Mar 2010 10:14:13 -0800
From:	Greg KH <greg@...ah.com>
To:	Alex Chiang <achiang@...com>
Cc:	sarah.a.sharp@...ux.intel.com, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] small xhci cleanups

On Tue, Mar 09, 2010 at 10:52:43AM -0700, Alex Chiang wrote:
> While trying to render aid and assistance for a USB3 issue that Sarah
> has been chasing, she grumbled in a private email that she was unable
> to coerce the build system to produce a module named "xhci_hcd".
> 
> This patch series shows one way to get around the Makefile intrinsics
> and create a module name of our choosing. There's probably a better
> way to do it, but it's beyond my makefile-fu.
> 
> The other change is to move all the debug code under
> CONFIG_XHCI_HCD_DEBUGGING, which is a straightforward change.
> 
> Thanks,
> /ac
> 
> ---
> 
> Alex Chiang (2):
>       USB: xhci: rename driver to xhci_hcd

I'm not opposed to this at all, but note, we should do it _now_ and not
hold on to this patch for the rest of the .34 development cycle
otherwise people are going to have a lot of trouble merging patches.

Sarah, mind if I take this one patch?

>       USB: xhci: move all debug code under CONFIG_XHCI_HCD_DEBUGGING

Does this conflict with Sarah's other debugging patch she just sent out?

thanks,

greg k-h
--
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/