linux-kernel - Re: question about drivers/mailbox/pcc.c

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.10.1503131529170.3275@hadrien>
Date:	Fri, 13 Mar 2015 15:29:43 +0100 (CET)
From:	Julia Lawall <julia.lawall@...6.fr>
To:	Ashwin Chaugule <ashwin.chaugule@...aro.org>
cc:	Jassi Brar <jassisinghbrar@...il.com>, daniel@...earbox.net,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: question about drivers/mailbox/pcc.c



On Fri, 13 Mar 2015, Ashwin Chaugule wrote:

> On 13 March 2015 at 05:12, Julia Lawall <julia.lawall@...6.fr> wrote:
> > Hello,
> >
> > The patch 86c22f8c9a3b from Wed Nov 12 19:59:38 2014 in linux-next
> > introduces a file that contains two exported functions:
> > pcc_mbox_request_channel and pcc_mbox_free_channel.  As far as I can see,
> > these functions are not used by any modules in the kernel source tree.
> > Is there some code coming that will use them, or should they be removed?
>
> There is code that depends on these functions being reviewed. CPPC is
> one client that is publicly being reviewed[1]. I know there are others
> (RASF), but I do not know their upstreaming status.

OK, thanks for the clarification.

julia


>
> Thanks,
> Ashwin.
>
> [1] - https://www.marc.info/?t=142239274200005&r=1&w=1
>
--
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/