All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: "Michael Chan" <mchan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, nsujir@broadcom.com,
	mcarlson@broadcom.com
Subject: Re: [PATCH 3/3 net-next] tg3: Add sysfs file to export sensor data
Date: Fri, 22 Jun 2012 17:59:34 -0700	[thread overview]
Message-ID: <20120622175934.2cc253b7@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1340237192-30052-3-git-send-email-mchan@broadcom.com>

On Wed, 20 Jun 2012 17:06:32 -0700
"Michael Chan" <mchan@broadcom.com> wrote:

> Some tg3 devices have management firmware that can export data such as
> temperature and other real time diagnostics data.  Export this data to
> sysfs so that userspace can access this information.
> 
> Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
> Signed-off-by: Nithin Nayak Sujir <nsujir@broadcom.com>
> Signed-off-by: Michael Chan <mchan@broadcom.com>

Linux has existing sensor api's that can be used by existing
services like SNMP. Wouldn't you like the it to just work with
existing code API's?

  parent reply	other threads:[~2012-06-23  0:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  0:06 [PATCH 1/3 net-next] tg3: Add common function tg3_ape_event_lock() Michael Chan
2012-06-21  0:06 ` [PATCH 2/3 net-next] tg3: Add APE scratchpad read and write functions Michael Chan
2012-06-21  0:06   ` [PATCH 3/3 net-next] tg3: Add sysfs file to export sensor data Michael Chan
2012-06-23  0:26     ` David Miller
2012-06-23  1:04       ` Michael Chan
2012-06-23 15:02         ` Ben Hutchings
2012-06-25 21:04           ` Michael Chan
2012-06-25 21:25             ` Ben Hutchings
2012-06-25 21:50               ` Michael Chan
2012-06-25 22:24               ` David Miller
2012-06-23  0:59     ` Stephen Hemminger [this message]
2012-06-23  1:32       ` Michael Chan

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=20120622175934.2cc253b7@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=mcarlson@broadcom.com \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=nsujir@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.