From: Stephen Warren <swarren@wwwdotorg.org>
To: axel.lin@gmail.com
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [linux-next][PATCH] regmap: fix build error if !CONFIG_DEBUG_FS
Date: Tue, 10 Apr 2012 09:23:00 -0600 [thread overview]
Message-ID: <4F845054.3070400@wwwdotorg.org> (raw)
In-Reply-To: <CAF+7xW=Rfj8vtoTCy7szgYpEMw1nW0HVR64b4mgJtjCoBbGi4A@mail.gmail.com>
On 04/10/2012 02:56 AM, Axel Lin wrote:
> 2012/4/10 Mark Brown <broonie@opensource.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.
prev parent reply other threads:[~2012-04-10 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 6:12 [linux-next][PATCH] regmap: fix build error if !CONFIG_DEBUG_FS Axel Lin
2012-04-10 8:43 ` Mark Brown
2012-04-10 8:56 ` Axel Lin
2012-04-10 15:23 ` Stephen Warren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F845054.3070400@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=axel.lin@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=swarren@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox