linux-kernel - Re: [BUILDFIX PATCH] v4l/dvb: add statics to avoid multiple definitions

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.LFD.1.10.0804260933370.2813@woody.linux-foundation.org>
Date:	Sat, 26 Apr 2008 09:38:51 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Adrian Bunk <bunk@...nel.org>
cc:	Harvey Harrison <harvey.harrison@...il.com>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUILDFIX PATCH] v4l/dvb: add statics to avoid multiple
 definitions

On Sat, 26 Apr 2008, Adrian Bunk wrote:
>
> I'm wondering what I am doing wrong since I already sent the same patch 
> and it went not into Linus' tree.

Why the hell are you even wondering?

You didn't send the patch to me. It's that damn simple. Harvey did.

I do *not* troll the internet for random patches to apply. But I do apply 
random patches that fix build errors etc, WHEN THEY ARE SENT TO ME.

That said, I'm not asking people to send patches directly to me when there 
is a maintainer that can handle it, but obviously when people do send 
obvious patches that I feel comfy applying and make sense to apply, I'll 
do so.

In other words, don't send cleanup patches to me when there is a 
maintainer, but if there is a build fix or an oops/security fix that you 
want to go into my tree asap, feel free to short-circuit maintainership.

This should be neither new nor surprising to anybody.

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