linux-kernel - Re: [PATCH] [TRIVIAL] v2: Fix declaration of intel_gmbus_{is_forced_bit/is_port

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: <20130506145230.GE5763@phenom.ffwll.local>
Date:	Mon, 6 May 2013 16:52:30 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	dl9pf@....de
Cc:	pageexec@...email.hu, daniel.vetter@...ll.ch, airlied@...ux.ie,
	intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [TRIVIAL] v2: Fix declaration of
 intel_gmbus_{is_forced_bit/is_port_falid} in i915 driver.

On Mon, May 06, 2013 at 02:52:08PM +0200, dl9pf@....de wrote:
> From: Jan-Simon Möller <dl9pf@....de>
> 
> 20130509: v2: (re-)add inline upon request.
> 
> Description:
> intel_gmbus_is_forced_bit is no extern as its body is right below.
> Likewise for intel_gmbus_is_port_valid.
> 
> This fixes a compilation issue with clang. An initial version of this patch
> was developed by PaX Team <pageexec at freemail.hu>.
> This is respin of this patch.
> 
> Signed-off-by: Jan-Simon Möller <dl9pf@....de>
> CC: pageexec@...email.hu
> CC: daniel.vetter@...ll.ch
> CC: airlied@...ux.ie
> CC: intel-gfx@...ts.freedesktop.org
> CC: dri-devel@...ts.freedesktop.org
> CC: linux-kernel@...r.kernel.org

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
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/