linux-kernel - Re: [GIT PULL] kbuild fixes

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: <4AD5730A.20906@msgid.tls.msk.ru>
Date:	Wed, 14 Oct 2009 10:43:22 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: [GIT PULL] kbuild fixes

Sam Ravnborg wrote:
> On Tue, Oct 13, 2009 at 11:19:52PM +0400, Michael Tokarev wrote:
>> Sam Ravnborg wrote:
[]
>>> And please - do not even think of asking me to do it.

>> How many patches should one send? How many trees one should
>> compare against and send different patch for, in case such
>> an obvious trivial cases?  If I'll provide this against
>> mainline, it wont apply to Sam's tree.

> mainline - a replacement patch would have been
> what I had expected to see.

That's what I didn't think of.  Due to the "trivialness" of
the whole thing (it's easier to go edit the target file
directly than to apply patches), and because.. well.. it
didn't occur to me ;)

> I took you patch and gave it a hopefully proper
> subject and applied it to kbuild-fixes.git.

Thank you Sam.

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