Fix bullet points in README.md
Each line was getting its own bullet point, leading to bullet points in the middle of sentences. This patch removes the excess bullet points. Change-Id: Ifb3a5e66fe6796236efe46e4dbda0ee2e89b0fcc
This commit is contained in:
parent
fd92a734be
commit
b6cac4cc46
12
README.md
12
README.md
|
@ -38,14 +38,14 @@ firmware version information is not a part of standard IPMI, but some servers
|
|||
are known to support it via custom OEM commands. If this is the case, follow
|
||||
these steps:
|
||||
- Add your generic retrieval function (stub) to the `OEMHandler` class in
|
||||
- `pyghmi/ipmi/oem/generic.py`. And please, document its intent, parameters and
|
||||
- expected return values.
|
||||
`pyghmi/ipmi/oem/generic.py`. And please, document its intent, parameters and
|
||||
expected return values.
|
||||
- Implement the specific methods that your server supports in subdirectories in
|
||||
- the `oem` folder (consider the `lenovo` submodule as an example). A OEM folder
|
||||
- will contain at least one class inheriting from `OEMHandler`, and optionally
|
||||
- helpers for running and parsing custom OEM commands.
|
||||
the `oem` folder (consider the `lenovo` submodule as an example). A OEM folder
|
||||
will contain at least one class inheriting from `OEMHandler`, and optionally
|
||||
helpers for running and parsing custom OEM commands.
|
||||
- Register mapping policies in `pyghmi/ipmi/oem/lookup.py` so pyghmi knows how
|
||||
- to associate a BMC session with the specific OEM code you implemented.
|
||||
to associate a BMC session with the specific OEM code you implemented.
|
||||
|
||||
A good way of testing the new feature is using `bin/pyghmiutil`. Just add an
|
||||
extension for the new feature you just implemented (as a new command) and call
|
||||
|
|
Loading…
Reference in New Issue