linux-kernel - Re: [RFC 2/3] drivers:staging:ti-st: mv ti_wilink

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]

Message-ID: <20100916195727.GH10397@kroah.com>
Date:	Thu, 16 Sep 2010 12:57:27 -0700
From:	Greg KH <greg@...ah.com>
To:	pavan_savoy@...com
Cc:	gregkh@...e.de, alan@...rguk.ukuu.org.uk,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 2/3] drivers:staging:ti-st: mv ti_wilink_st to include/

On Fri, Sep 10, 2010 at 03:58:57PM -0400, pavan_savoy@...com wrote:
> From: Pavan Savoy <pavan_savoy@...com>
> 
> Move the ti_wilink_st header (previously st.h) to include/linux
> directory. This header is to be included by all protocol drivers viz'
> bluetooth drivers, FM V4L2 and GPS generic character device driver.
> It also serves the core shared transport driver.

Ah, so the individual drivers will be in the different parts of the
kernel?  Like drivers/char and other places?  That makes sense why they
should be using a file in include/linux/

But just make the file that name now, in the staging directory.  That
way when we move the code out, it's easier to do so (we don't have to do
this 3 patch series.)

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/