[PATCH linux dev-4.7 7/8] ipmi: maintain a request expiry list

Patrick Williams patrick at stwcx.xyz
Tue Nov 8 02:02:57 AEDT 2016


On Mon, Nov 07, 2016 at 06:25:41AM +0100, Cédric Le Goater wrote:
> Hello,
> 
> On 11/04/2016 07:22 PM, Brendan Higgins wrote:
> > Thanks for roping me in,
> > 
> > Patrick summed up my intention perfectly. IPMI messages will be structured 
> > the same and use compatible fields, but would allow for different flow control. 
> > In particular, the goal is to allow multiple requests and responses under a 
> > single sequence number.
> 
> So if the combinations of { Seq, Command, NetFn } values are unique, we 
> should be fine. The expiry list patch needs to be more precise when doing 
> matching though.

Brendan was implying that this is incorrect for OEM commands.

Brendan can you clarify?

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20161107/5d939f4c/attachment.sig>


More information about the openbmc mailing list