linux-kernel - Re: [PATCH 2/6] genirq: Fix the documentation of request_percpu

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: <20150708.140518.1912932449236610733.davem@davemloft.net>
Date:	Wed, 08 Jul 2015 14:05:18 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	maxime.ripard@...e-electrons.com
Cc:	tglx@...utronix.de, gregory.clement@...e-electrons.com,
	jason@...edaemon.net, andrew@...n.ch,
	sebastian.hesselbarth@...il.com,
	thomas.petazzoni@...e-electrons.com, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH 2/6] genirq: Fix the documentation of request_percpu_irq

From: Maxime Ripard <maxime.ripard@...e-electrons.com>
Date: Fri,  3 Jul 2015 16:25:47 +0200

> The documentation of request_percpu_irq is confusing and suggest that the
> interrupt is not enabled at all, while it is actually enabled on the local
> CPU.
> 
> Clarify that.
> 
> Signed-off-by: Maxime Ripard <maxime.ripard@...e-electrons.com>

You should submit this separately to the IRQ layer maintainers, rather
than try to include it in an unrelated set of changes targetting net-next.

Thanks.
--
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/