From: Patrick Williams <patrick@stwcx.xyz>
To: tomjose <tomjose@linux.vnet.ibm.com>
Cc: Li Nan <william.bjlinan@hotmail.com>,
Adriana Kobylak <anoo@linux.vnet.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: IPMI LAN command story design - try 3rd send
Date: Fri, 4 Nov 2016 09:14:55 -0500 [thread overview]
Message-ID: <20161104141455.GE17105@heinlein.lan> (raw)
In-Reply-To: <581C8C7D.8080702@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
Tom,
On Fri, Nov 04, 2016 at 06:56:21PM +0530, tomjose wrote:
> The Set Channel access command was decided to be used to mark the end of
> a setting LAN configuration transaction.
The IPMI spec for the SetLanConfig has a parameter 'Set In Progress'
which states: 10b = commit write. Why are we not utilizing that? Maybe
in addition to Set Channel Access?
I don't see anything in the Set Channel Access command description that
would be obvious as a mechanism for updating IP addresses. Was that
just quick behavior we decided to do for Barreleye? Is there any reason
why we would not deprecate that behavior in favor of the Set In
Progress / commit write?
--
Patrick Williams
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-04 14:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 13:59 IPMI LAN command story design - try 3rd send Li Nan
[not found] ` <57F37746.6040304@linux.vnet.ibm.com>
2016-10-04 14:51 ` Patrick Williams
2016-10-17 6:55 ` Li Nan
2016-11-03 16:22 ` Li Nan
2016-11-04 13:26 ` tomjose
2016-11-04 14:14 ` Patrick Williams [this message]
2016-11-04 17:50 ` tomjose
2016-11-07 3:50 ` Patrick Williams
2016-11-08 10:45 ` tomjose
2016-11-08 11:41 ` Patrick Williams
2016-11-10 2:32 ` Li Nan
2017-12-13 3:08 ` Jeremy Kerr
2017-12-13 16:55 ` Chris Austen
2017-12-14 11:23 ` Tom Joseph
2017-12-14 12:30 ` Jeremy Kerr
2017-12-14 13:03 ` Tom Joseph
2017-12-14 14:45 ` Jeremy Kerr
2017-12-14 16:26 ` Vernon Mauery
2017-12-14 21:55 ` Jeremy Kerr
2017-12-14 23:35 ` Patrick Venture
2017-12-15 5:08 ` Tom Joseph
2017-12-18 16:19 ` Vernon Mauery
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=20161104141455.GE17105@heinlein.lan \
--to=patrick@stwcx.xyz \
--cc=anoo@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tomjose@linux.vnet.ibm.com \
--cc=william.bjlinan@hotmail.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.