linux-kernel - Re: mips: CONF_CM

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]

Date:	Fri, 13 Jun 2008 14:55:38 +0100
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Atsushi Nemoto <anemo@....ocn.ne.jp>
Cc:	adrian.bunk@...ial.fi, chris@...s.com, linux-mips@...ux-mips.org,
	linux-kernel@...r.kernel.org
Subject: Re: mips: CONF_CM_DEFAULT build error

On Mon, Jun 02, 2008 at 01:28:14AM +0900, Atsushi Nemoto wrote:

> > Commit 351336929ccf222ae38ff0cb7a8dd5fd5c6236a0
> > ([MIPS] Allow setting of the cache attribute at run time.)
> > causes the following build error with pnx8550-jbs_defconfig
> > and pnx8550-stb810_defconfig:
> 
> I wondered why the commit has my S-O-B, and finally found that I had
> fixed a section mismatch caused by the original patch (on queue tree
> on linux-mips.org) and Ralf had folded my fix into the original patch,
> with my S-O-B.  Folding on the queue tree will be good on many case,
> but sometimes a bit confusing. :-)

Yes, I try to merge any follow on patches into the original patch as long
as that one is still sitting in the patch queue.  Since that result in
bugs getting fixes before they ever show up in any of the more static
trees, that is the MIPS or kernel.org git trees there is little point in
documenting bugs "that never existed" and their "non-fixes" ;-)

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