linux-kernel - Re: [PATCH 2/2 -tip] drm/i915: intel_lvds.c fix section mismatch warning

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: <1243607316.3210.4.camel@localhost.localdomain>
Date:	Fri, 29 May 2009 19:58:36 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Len Brown <lenb@...nel.org>, Dave Airlie <airlied@...ux.ie>,
	drm list <dri-devel@...ts.sf.net>, Ingo Molnar <mingo@...e.hu>,
	Eric Anholt <eric@...olt.net>, mjg@...hat.com,
	Sam Ravnborg <sam@...nborg.org>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jarod Wilson <jarod@...hat.com>
Subject: Re: [PATCH 2/2 -tip] drm/i915: intel_lvds.c fix section mismatch
 warning

Hi Andrew,

On Fri, 2009-05-29 at 09:34 -0400, Jarod Wilson wrote:
> On Friday 29 May 2009 02:16:35 Jaswinder Singh Rajput wrote:
> > I am not sure where this patch should go.
> > 
> > So I am also mailing to Andrew and Dave, it they find this useful then
> > they can add in their tree.
> 
> Dave is on vacation a bit longer, iirc. Not entirely sure where else
> this might go either. I'm sure *someone* will pick it up sooner or
> later... In any case, thanks for the fix for my flub.
> 
> Acked-by: Jarod Wilson <jarod@...hat.com>
> 

Can you accept this patch with Jarod Ack as Dave is on vacation and Ingo
is still busy with perfcounter ;-)

Thanks,
--
JSR

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