> User applications need to declare this ipmi_device buffer and pass on > to UDM functions. Sometimes, user may access members of this struct > directly to pass advanced arguments.
Similar to the issues we hit in IPMI 2.0 with fiid, I'm worried that not hiding the implementation may bite us later on. Al -- Albert Chu [EMAIL PROTECTED] 925-422-5311 Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory ----- Original Message ----- From: Anand Babu <[EMAIL PROTECTED]> Date: Wednesday, January 25, 2006 12:16 pm Subject: Re: [Freeipmi-devel] struct ipmi_device > ,----[ Albert Chu <[EMAIL PROTECTED]> ] > | Hi guys, > | > | I just noticed you have struct ipmi_device in ipmi-interface.h. Is > | there a reason you believe this structure should be made public? I > | would think it should be made private so the abstraction can stay > | hidden. > `---- > User applications need to declare this ipmi_device buffer and pass on > to UDM functions. Sometimes, user may access members of this struct > directly to pass advanced arguments. > > -- > Albert Chu > [EMAIL PROTECTED] > 925-422-5311 > Computer Scientist > High Performance Systems Division > Lawrence Livermore National Laboratory > > > > > _______________________________________________ > Freeipmi-devel mailing list > Freeipmiemail@example.com > http://lists.gnu.org/mailman/listinfo/freeipmi-devel > > -- > Anand Babu > GPG Key ID: 0x62E15A31 > Blog [http://ab.freeshell.org] > The GNU Operating System [http://www.gnu.org] > _______________________________________________ Freeipmi-devel mailing list Freeipmifirstname.lastname@example.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel