From: Johnathan Mantey <johnathanx.mantey@intel.com>
To: Paul Fertser <fercerpav@gmail.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: SATA hotplug notifications for BMC inventory updates
Date: Fri, 9 Sep 2022 07:12:21 -0700 [thread overview]
Message-ID: <89592b7f-784c-d94c-8a81-57cb49a3bcce@intel.com> (raw)
In-Reply-To: <Yxr6OmHDrzQVSaYr@home.paul.comp>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On 9/9/22 01:32, Paul Fertser wrote:
> Hello Johnathan,
>
> On Wed, Sep 07, 2022 at 07:36:08AM -0700, Johnathan Mantey wrote:
<snip>
>> Paul, this question now crosses a demarcation line. As a contract
>> worker I'm not comfortable discussing the topics you raise in that
>> paragraph.
> I'm not fluent in business slang so I take it you mean the feature
> might be nice but Intel doesn't want the OpenBMC community to have
> it. Well, too bad.
What I'm trying to convey is that as a contract worker I have access to
some information I may not be authorized to divulge. This is a public
forum, and I need to tread carefully so that I don't divulge information
that impacts my employment.
The starting point for this conversation was HDD insertion/removal event
detection.
Which then evolved to HDD MFR/Model Num access.
Which then evolved into RAID controllers.
It may turn out that Intel does want this feature as part of OBMC.
It may turn out that Intel is amenable to the community implementing a
RAID/BMC feature.
The transition to RAID controller has initiated an investigation into
what Intel may be willing to enable regarding OBMC.
--
Johnathan Mantey
Senior Software Engineer
*azad te**chnology partners*
Contributing to Technology Innovation since 1992
Phone: (503) 712-6764
Email: johnathanx.mantey@intel.com
[-- Attachment #2: Type: text/html, Size: 2592 bytes --]
next prev parent reply other threads:[~2022-09-09 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 11:11 SATA hotplug notifications for BMC inventory updates Paul Fertser
2022-09-06 15:53 ` Johnathan Mantey
[not found] ` <17841662532977@mail.yandex-team.ru>
2022-09-07 14:04 ` Johnathan Mantey
2022-09-07 14:26 ` Paul Fertser
2022-09-07 14:16 ` Paul Fertser
2022-09-07 14:36 ` Johnathan Mantey
2022-09-09 8:32 ` Paul Fertser
2022-09-09 14:12 ` Johnathan Mantey [this message]
2022-09-09 21:19 ` Bills, Jason M
2022-09-15 15:32 ` Paul Fertser
2022-09-15 15:05 ` Paul Fertser
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=89592b7f-784c-d94c-8a81-57cb49a3bcce@intel.com \
--to=johnathanx.mantey@intel.com \
--cc=fercerpav@gmail.com \
--cc=openbmc@lists.ozlabs.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 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.