Re: [PATCH v2 13/21] ipmi: kcs_bmc: Decouple the IPMI chardev from the core

On Fri, 9 Apr 2021, at 14:05, Zev Weiss wrote: > On Fri, Mar 19, 2021 at 01:27:44AM CDT, Andrew Jeffery wrote: > >Now that we have untangled the data-structures, split the userspace > >interface out into its own module. Userspace interfaces and drivers are > >registered to the KCS BMC core to su

Re: [PATCH v2 13/21] ipmi: kcs_bmc: Decouple the IPMI chardev from the core

On Fri, Mar 19, 2021 at 01:27:44AM CDT, Andrew Jeffery wrote: >Now that we have untangled the data-structures, split the userspace >interface out into its own module. Userspace interfaces and drivers are >registered to the KCS BMC core to support arbitrary binding of either. > >Signed-off-by: Andre

RE: [PATCH v2 13/21] ipmi: kcs_bmc: Decouple the IPMI chardev from the core

m.org > Subject: [PATCH v2 13/21] ipmi: kcs_bmc: Decouple the IPMI chardev from the > core > > Now that we have untangled the data-structures, split the userspace interface > out into its own module. Userspace interfaces and drivers are registered to > the > KCS BMC core to

[PATCH v2 13/21] ipmi: kcs_bmc: Decouple the IPMI chardev from the core

Now that we have untangled the data-structures, split the userspace interface out into its own module. Userspace interfaces and drivers are registered to the KCS BMC core to support arbitrary binding of either. Signed-off-by: Andrew Jeffery --- drivers/char/ipmi/Kconfig | 13 + d