linux-kernel - Re: [PATCH] drivers:misc: ti-st: fix debugging code

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:	Wed, 2 Mar 2011 20:06:05 -0800
From:	Greg KH <greg@...ah.com>
To:	pavan_savoy@...com
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: [PATCH] drivers:misc: ti-st: fix debugging code

On Wed, Mar 02, 2011 at 03:59:56AM -0600, pavan_savoy@...com wrote:
> From: Pavan Savoy <pavan_savoy@...com>
> 
> debug code in TI-ST driver can be enabled by #defining
> DEBUG in the first line of the code and in case debugfs
> is mounted, the 2 entries in /sys/kernel/debug/ti-st/ will
> also provide useful information.
> These 2 were broken because of the recent changes to the parsing
> logic and the registration mechanism of the protocol drivers,
> this patch fixes them.
> 
> Signed-off-by: Pavan Savoy <pavan_savoy@...com>
> ---
>  drivers/misc/ti-st/st_core.c |   18 ++++--------------
>  1 files changed, 4 insertions(+), 14 deletions(-)

What tree was this made against?  I can't seem to apply it to my
staging-next tree.

confused,

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/