From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] misc: fuse: Add efuse driver for Tegra
Date: Thu, 19 Dec 2013 12:20:01 -0700 [thread overview]
Message-ID: <52B346E1.2030508@wwwdotorg.org> (raw)
In-Reply-To: <20131219175931.GA18004@kroah.com>
On 12/19/2013 10:59 AM, Greg KH wrote:
> On Thu, Dec 19, 2013 at 05:54:30PM +0200, Peter De Schrijver wrote:
>> + pr_info("Tegra Revision: %s SKU: %d CPU Process: %d Core Process: %d\n",
>> + tegra_revision_name[sku_info->revision],
>> + sku_info->sku_id, sku_info->cpu_process_id,
>> + sku_info->core_process_id);
>
> Why pollute the kernel log with this type of thing? Who really needs
> it?
We already print this; I guess this series is just moving where that
happens. It has proved useful to me in the past so I know which chip rev
I'm using, but I guess if this all gets exported to sysfs somewhere else
in this series, I could just go read those files in the future...
next prev parent reply other threads:[~2013-12-19 19:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 15:54 [PATCH 0/6] efuse driver for Tegra Peter De Schrijver
2013-12-19 15:54 ` [PATCH 1/6] ARM: tegra: export apb dma readl/writel Peter De Schrijver
2013-12-19 15:54 ` [PATCH 2/6] misc: fuse: Add efuse driver for Tegra Peter De Schrijver
2013-12-19 17:59 ` Greg KH
2013-12-19 19:20 ` Stephen Warren [this message]
2013-12-19 19:43 ` Greg KH
2013-12-19 15:54 ` [PATCH 3/6] ARM: tegra: Add efuse bindings Peter De Schrijver
2013-12-19 15:54 ` [PATCH 4/6] ARM: tegra: rework fuse.c Peter De Schrijver
2014-01-02 12:37 ` Linus Walleij
2014-01-02 14:32 ` Peter De Schrijver
2014-01-02 17:03 ` Linus Walleij
2013-12-19 15:54 ` [PATCH 5/6] ARM: Tegra: remove speedo files Peter De Schrijver
2013-12-19 15:54 ` [PATCH 6/6] misc: enable fuse drivers Peter De Schrijver
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=52B346E1.2030508@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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).