From: Ed Tanous <ed@tanous.net>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: Zhikui Ren <zhikui.ren@intel.com>,
Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
Andrew Jeffery <andrew@aj.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Jayashree D <jayashree-d@hcl.com>,
Amithash Prasad <amithash@fb.com>,
Kumar Thangavel <kumarthangavel.hcl@gmail.com>,
"Velumani T-ERS, HCLTech" <velumanit@hcl.com>
Subject: Re: Creating Hard Shutdown interfaces/alarm for NIC Sensor
Date: Mon, 16 Aug 2021 12:32:38 -0700 [thread overview]
Message-ID: <CACWQX82LHoOPPMPzYwVmcT45hr=U3jb=cN0FQXVn4YhGStHcig@mail.gmail.com> (raw)
In-Reply-To: <YRq0fULpBC1hJwhw@heinlein>
On Mon, Aug 16, 2021 at 11:54 AM Patrick Williams <patrick@stwcx.xyz> wrote:
>
> On Mon, Aug 16, 2021 at 09:27:58PM +0530, Kumar Thangavel wrote:
> > Gentle Reminder. Any suggestions/idea on this.
>
> Hi Kumar,
>
> Can you frame your original email with a question?
>
> I'm not versed in the details here enough to know what you're underlying
> concern is. When I read the email I see mostly a list of "facts".
>
> I suspect others are similarly not responding because they don't know what you
> want to know or where your doubts are.
I wasn't responding because there's been several discussions on almost
this exact use case, as well as patchsets to add the new types and
interfaces. To reiterate Patricks comment, I was hoping you'd search
for them and either jump into those discussions where the work is
being done, or propose some more pointed questions once you got more
versed on what already exists along those lines.
>
> --
> Patrick Williams
prev parent reply other threads:[~2021-08-16 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 11:21 Creating Hard Shutdown interfaces/alarm for NIC Sensor Kumar Thangavel
2021-08-16 15:57 ` Kumar Thangavel
2021-08-16 18:54 ` Patrick Williams
2021-08-16 19:32 ` Ed Tanous [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='CACWQX82LHoOPPMPzYwVmcT45hr=U3jb=cN0FQXVn4YhGStHcig@mail.gmail.com' \
--to=ed@tanous.net \
--cc=amithash@fb.com \
--cc=andrew@aj.id.au \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=jayashree-d@hcl.com \
--cc=kumarthangavel.hcl@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=velumanit@hcl.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 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).