linux-kernel - Re: [linux-next][PATCH] regmap: fix build error if !CONFIG_DEBUG

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAF+7xW=Rfj8vtoTCy7szgYpEMw1nW0HVR64b4mgJtjCoBbGi4A@mail.gmail.com>
Date:	Tue, 10 Apr 2012 16:56:34 +0800
From:	Axel Lin <axel.lin@...il.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-kernel@...r.kernel.org, Stephen Warren <swarren@...dia.com>
Subject: Re: [linux-next][PATCH] regmap: fix build error if !CONFIG_DEBUG_FS

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.

Regards,
Axel
--
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/