linux-kernel - Re: [PATCH] x86: unused variable in dma_alloc_coherent_gfp

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]

Date:	Tue, 9 Sep 2008 09:13:38 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	steven@...inklabs.net, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, hpa@...or.com
Subject: Re: [PATCH] x86: unused variable in dma_alloc_coherent_gfp_flags()


* FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:

> On Tue, 9 Sep 2008 08:57:36 +0200
> Ingo Molnar <mingo@...e.hu> wrote:
> 
> > 
> > * Steven Noonan <steven@...inklabs.net> wrote:
> > 
> > > Fixed a warning caused by a badly placed ifdef.
> > > 
> > > Signed-off-by: Steven Noonan <steven@...inklabs.net>
> > 
> > applied to tip/x86/iommu - thanks Steven,
> 
> Did you apply the same patch yesterday?
> 
> http://lkml.org/lkml/2008/9/8/274

yes, but i havent pushed it out in time yesterday night. In such 
scenarios i generally zap the patch i generated and replace it with the 
fix that is being sent against the last publicly available tree. That is 
what happened here too. This makes it all symmetric and fair (i as a 
maintainer have no time advantage to get fixes in first) and it also 
teaches me to push out fixes faster :-)

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