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
| ||
|
Date: Tue, 10 Apr 2012 09:23:00 -0600 From: Stephen Warren <swarren@...dotorg.org> To: axel.lin@...il.com CC: Mark Brown <broonie@...nsource.wolfsonmicro.com>, Stephen Rothwell <sfr@...b.auug.org.au>, linux-kernel@...r.kernel.org, Stephen Warren <swarren@...dia.com> Subject: Re: [linux-next][PATCH] regmap: fix build error if !CONFIG_DEBUG_FS On 04/10/2012 02:56 AM, Axel Lin wrote: > 2012/4/10 Mark Brown <broonie@...nsource.wolfsonmicro.com>: >> On Tue, Apr 10, 2012 at 02:12:47PM +0800, Axel Lin wrote: >>> Fix build error introduced by commit 9eba4d >>> "regmap: fix compilation when !CONFIG_DEBUG_FS". >> >> I've no idea what tree you're testing against but Stephen's fix is >> needed for -next. > > I'm testing with today's linux-next tree. > It's strange in today's linux-next tree that "git show 79c64d5" can > show the commit, > but git log cannot find commit 79c64d5. I checked internal.h and regmap.c in next-20120410 and they seem exactly matched at present. Yes, commit 79c64d5 doesn't exist. The real commit ID is d3c242e1f22f5dfed009296ee45ce896153f0b53 (i.e. the one right before commit 9eba4d). This is because the commit in question got moved between topic branches. -- 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/
Powered by blists - more mailing lists