From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: error detecting cacheinfo
Date: Tue, 11 Nov 2014 18:05:23 +0000 [thread overview]
Message-ID: <54624FE3.1090109@arm.com> (raw)
In-Reply-To: <CAOMZO5Af6Rh7zDBGu7cNarENV-+Pr5CWaj7HZMXKq9_QCGk7tg@mail.gmail.com>
On 11/11/14 16:52, Fabio Estevam wrote:
> Sudeep,
>
> I am running linux-next 20141111 and since commit 246246cbde5e ("
> drivers: base: support cpu cache information interface to userspace
> via sysfs") I am getting the following error on a mx6:
>
> [ 1.253691] error detecting cacheinfo..cpu0
>
> What would be the correct way to fix this error?
>
Sorry for that. I think it should be changed to debug as it's noisy in
boot message. I will post a patch to silence that and check if Greg can
pick up this.
Since the changes in my original series[1] are across multiple
architectures (some of them is yet test), I asked Greg to pull only the
core support. I have the architecture specific patches 5-11 to follow
which I am targeting v3.20.
Regards,
Sudeep
[1] https://lkml.org/lkml/2014/9/30/347
prev parent reply other threads:[~2014-11-11 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 16:52 error detecting cacheinfo Fabio Estevam
2014-11-11 18:05 ` Sudeep Holla [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=54624FE3.1090109@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).