From: "he.huang" <he.huang@linux.intel.com>
To: "Brad Bishop" <bradleyb@fuzziesquirrel.com>, "ed" <ed@tanous.net>,
"jae.hyun.yoo" <jae.hyun.yoo@linux.intel.com>,
"vernon.mauery" <vernon.mauery@linux.intel.com>,
"openbmc" <openbmc@lists.ozlabs.org>
Subject: Re: Re: Add size property of EEPROM device
Date: Thu, 26 Nov 2020 08:27:58 +0800 [thread overview]
Message-ID: <5FBEF68B.3020007@linux.intel.com> (raw)
In-Reply-To: <4e839c2d6723f6b2d6c4a990869093c09988d6d4.camel@fuzziesquirrel.com>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Hi Brad,
Yes, eeprom driver could help the requirement partially.
As Ed's comments on the patch, we still need the size in the upper level such as IPMI command handler, to differentiate the error between writing failed and writing out of the range, and return the correct complete code.
Thanks.
2020-11-26
Helen.huang
发件人：Brad Bishop <bradleyb@fuzziesquirrel.com>
发送时间：2020-11-25 23:36
主题：Re: Add size property of EEPROM device
收件人："he.huang"<he.huang@linux.intel.com>,"ed"<ed@tanous.net>,"jae.hyun.yoo"<jae.hyun.yoo@linux.intel.com>,"vernon.mauery"<vernon.mauery@linux.intel.com>,"openbmc"<openbmc@lists.ozlabs.org>
抄送：
On Tue, 2020-11-24 at 15:31 +0800, he.huang wrote:
> The requirement comes from:
> When we write to the EEPROM we need the size to ensure that we won't
> write out of the range and return the correct complete code.
Don't the eeprom drivers prevent this?
[-- Attachment #2: Type: text/html, Size: 3401 bytes --]
prev parent reply other threads:[~2020-11-26 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 7:31 Add size property of EEPROM device he.huang
2020-11-25 15:36 ` Brad Bishop
2020-11-26 0:27 ` he.huang [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=5FBEF68B.3020007@linux.intel.com \
--to=he.huang@linux.intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=ed@tanous.net \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=vernon.mauery@linux.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.