linux-kernel - Re: [PATCH 07/12] n_tracerouter and n

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]

Date:	Thu, 17 Feb 2011 11:21:54 -0800
From:	Greg KH <greg@...ah.com>
To:	james_p_freyensee@...ux.intel.com, Alan Cox <alan@...ux.intel.com>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org,
	suhail.ahmed@...el.com
Subject: Re: [PATCH 07/12] n_tracerouter and n_tracesink additions.

On Tue, Feb 08, 2011 at 11:34:52AM -0800, james_p_freyensee@...ux.intel.com wrote:
> From: J Freyensee <james_p_freyensee@...ux.intel.com>
> 
> This patch adds line discipline numbers to n_tracerouter and
> n_tracesink line disciplines for the Intel-Atom PTI implementation
> for mobile devices.
> 
> Signed-off-by: J Freyensee <james_p_freyensee@...ux.intel.com>
> ---
>  include/linux/tty.h |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/include/linux/tty.h b/include/linux/tty.h
> index 54e4eaa..c507f53 100644
> --- a/include/linux/tty.h
> +++ b/include/linux/tty.h
> @@ -50,6 +50,8 @@
>  #define N_CAIF		20      /* CAIF protocol for talking to modems */
>  #define N_GSM0710	21	/* GSM 0710 Mux */
>  #define N_TI_WL		22	/* for TI's WL BT, FM, GPS combo chips */
> +#define N_TRACESINK	23	/* Trace data routing for MIPI P1149.7 */
> +#define N_TRACEROUTER	24	/* Trace data routing for MIPI P1149.7 */

Two new ones?  Really?  Alan, no objection from you on this?

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/