linux-kernel - Re: MIPS: BMIPS: Enable GZIP ramdisk and timed printks

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:	Thu, 12 Nov 2015 11:36:50 +0100
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Andreas Ziegler <andreas.ziegler@....de>
Cc:	Florian Fainelli <f.fainelli@...il.com>,
	Kevin Cernekee <cernekee@...il.com>,
	Dragan Stancevic <dragan.stancevic@...il.com>,
	blogic@...nwrt.org, Jonas Gorski <jogo@...nwrt.org>,
	linux-mips@...ux-mips.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Valentin Rothberg <valentinrothberg@...il.com>,
	Paul Bolle <pebolle@...cali.nl>
Subject: Re: MIPS: BMIPS: Enable GZIP ramdisk and timed printks

On Thu, Nov 12, 2015 at 11:18:30AM +0100, Andreas Ziegler wrote:

> Hi Florian,
> 
> your patch "MIPS: BMIPS: Enable GZIP ramdisk and timed printks"
> showed up as commit fb9e5642aa9e in linux-next today (that is,
> next-20151112). I noticed it because we (a research group from
> Erlangen[0]) are running daily checks on linux-next.
> 
> Your commit adds two entries to arch/mips/configs/bmips_stb_defconfig,
> but one of them has a typo (line 37):
> 
> CONFIG_PRINK_TIME=y
> 
> which should instead say (notice the missing 'T'):
> 
> CONFIG_PRINTK_TIME=y
> 
> Not sure how this got two Reviewed-by's, as this simple mistake could
> have been easily spotted by running scripts/checkkconfigsymbols.py on
> the patch.

Sigh, fixed.

  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/