All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tanous <ed@tanous.net>
To: Kumar Thangavel <thangavel.k@hcl.com>
Cc: Zhikui Ren <zhikui.ren@intel.com>,
	Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
	Patrick Venture <venture@google.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Vernon Mauery <vernon.mauery@linux.intel.com>,
	"Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
	Patrick Williams <patrickw3@fb.com>
Subject: Re: Fault handling(Threshold exceeds/low) in Fan and NIC sensors
Date: Fri, 13 Nov 2020 12:44:14 -0800	[thread overview]
Message-ID: <CACWQX81k6M6acw0VL3aYA_uqpNsEUjZ3DhiAQp_mXLbGJU87=g@mail.gmail.com> (raw)
In-Reply-To: <HK0PR04MB2964AA77874471609F0B25BEFDE60@HK0PR04MB2964.apcprd04.prod.outlook.com>

On Fri, Nov 13, 2020 at 8:31 AM Kumar Thangavel <thangavel.k@hcl.com> wrote:
>
>          Could you please provide your suggestions on this.

I'm having a little trouble following your email.  Dbus-sensors has
the ability to mask thresholds where appropriate, the platform
specifics of which are already captured in the config file definition.
If there's some configurable masking needed that's new, we can
certainly add it, but I'd recommend looking at the existing threshold
masking before adding anything new to see if what's there meets your
needs.  If you have some concrete things you'd like to see added, I'm
happy to talk in more detail, just at this point, I have no idea what
you're looking to solve, so you might want to be slightly more
specific, and reference the existing threshold even masking in your
proposed changes.

Cheers,

-Ed

  reply	other threads:[~2020-11-13 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 16:30 Fault handling(Threshold exceeds/low) in Fan and NIC sensors Kumar Thangavel
2020-11-13 20:44 ` Ed Tanous [this message]
2020-11-16 13:05   ` Kumar Thangavel
2020-11-16 15:59     ` Ed Tanous
2020-11-17 11:59       ` Kumar Thangavel
2020-11-20 17:10         ` Matt Spinler

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='CACWQX81k6M6acw0VL3aYA_uqpNsEUjZ3DhiAQp_mXLbGJU87=g@mail.gmail.com' \
    --to=ed@tanous.net \
    --cc=jae.hyun.yoo@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrickw3@fb.com \
    --cc=thangavel.k@hcl.com \
    --cc=velumanit@hcl.com \
    --cc=venture@google.com \
    --cc=vernon.mauery@linux.intel.com \
    --cc=zhikui.ren@intel.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.