<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/OpenBmc/bmcweb.git/redfish-core/include/generated/enums/settings.hpp, branch master</title>
<subtitle>A do everything Redfish, KVM, GUI, and DBus webserver for OpenBMC (mirror)</subtitle>
<id>https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/atom?h=master</id>
<link rel='self' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/'/>
<updated>2026-05-19T19:16:28+00:00</updated>
<entry>
<title>Move to Redfish 2026.1</title>
<updated>2026-05-19T19:16:28+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2026-05-19T19:16:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=df2c4aac86d556cd3d618588ce819d63c3e01caf'/>
<id>urn:sha1:df2c4aac86d556cd3d618588ce819d63c3e01caf</id>
<content type='text'>
One line change and rerun the script. 2026.1 includes new properties.
The overview is at [1].

[1]: https://www.dmtf.org/sites/default/files/Redfish_Release_2026.1_Overview.pdf

Tested: Inspection only.

Change-Id: I007f074128e278fb267ee4de3b9cbab22d6336df
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Move clang-off / clang-on to catch scope</title>
<updated>2026-01-26T20:35:54+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2026-01-26T15:54:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=ac69e77ea938e8c2a5bd3dad258cdafd9d3182b7'/>
<id>urn:sha1:ac69e77ea938e8c2a5bd3dad258cdafd9d3182b7</id>
<content type='text'>
As a comment in https://gerrit.openbmc.org/c/openbmc/bmcweb/+/86868
suggested "You might also consider moving this up a line so you catch
the scope on both sides."

This enforces just the slightest bit more clang-format.

Rerun script.

Tested: Builds. Manual changes to script only. Rest generated.

Change-Id: I8ff01befc56c576716f5d83bd90763354b1ff0c5
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Modify enum generation for clang</title>
<updated>2026-01-23T14:50:11+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2026-01-22T18:43:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=30552246534559518cdfa61618e2009a1b4b5769'/>
<id>urn:sha1:30552246534559518cdfa61618e2009a1b4b5769</id>
<content type='text'>
Clang-format was unhappy with the new
redfish-core/include/generated/enums/switch.hpp in 2025.4

```
diff --git a/redfish-core/include/generated/enums/switch.hpp b/redfish-core/include/generated/enums/switch.hpp
index 6acf6e28..cabc8562 100644
--- a/redfish-core/include/generated/enums/switch.hpp
+++ b/redfish-core/include/generated/enums/switch.hpp
@@ -5,7 +5,7 @@

 namespace switch
 {
-// clang-format off
+    // clang-format off
```

Move turning clang-format off before the namespace fixes.
¯\_(ツ)_/¯
Do that in generate_schema_enums.py and rerun update_schemas.py.

Adding 4 spaces before the clang-format off broke other generated
enums. Broke out from 2025.4.

Tested: Visual and build only.

Change-Id: Ic03aa558b405957f15035570d376c46c545906c0
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Use SPDX identifiers</title>
<updated>2025-01-20T18:44:54+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>etanous@nvidia.com</email>
</author>
<published>2024-09-10T20:50:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=40e9b92ec19acffb46f83a6e55b18974da5d708e'/>
<id>urn:sha1:40e9b92ec19acffb46f83a6e55b18974da5d708e</id>
<content type='text'>
SPDX identifiers are simpler, and reduce the amount of cruft we have in
code files.  They are recommended by linux foundation, and therefore we
should do as they allow.

This patchset does not intend to modify any intent on any existing
copyrights or licenses, only to standardize their inclusion.

[1] https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects

Change-Id: I935c7c0156caa78fc368c929cebd0f068031e830
Signed-off-by: Ed Tanous &lt;etanous@nvidia.com&gt;
</content>
</entry>
<entry>
<title>Pull in 2024.1 schemas</title>
<updated>2024-06-18T15:23:23+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2024-06-18T14:31:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=f2a8e57ede74a8252100b2281e3f4d170aa69391'/>
<id>urn:sha1:f2a8e57ede74a8252100b2281e3f4d170aa69391</id>
<content type='text'>
Redfish released 2024.1 in May.
https://www.dmtf.org/content/redfish-release-20241-now-available

"The bundle includes 29 schema updates and additional developer
resources." There was a request on the discord server to pull this in.

Changed 1 line scripts/update_schemas.py and reran the tool.

Tested: None. Inspection only. Picking up new schemas hasn't caused
problems in the past.

Change-Id: I44f08ab56ad2f97b757b48003ac97a2f914bd8ea
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Generate Redfish enums from schemas</title>
<updated>2022-12-08T20:08:01+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>edtanous@google.com</email>
</author>
<published>2022-03-14T21:56:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=0ec8b83db7e8629c721c0e632de702bf1018f58f'/>
<id>urn:sha1:0ec8b83db7e8629c721c0e632de702bf1018f58f</id>
<content type='text'>
OpenBMC tends to have a significant problem in doing the appropriate
lookups from the schema files, and many bugs have been injected by users
picking a bad enum, or mistyping the casing of an enum value.

At the same time, nlohmann::json has recently added first class support
for enums, https://json.nlohmann.me/features/enum_conversion/

This commit attempts to build a set of redfish includes file with all
the available Redfish enums in an easy to use enum class.  This makes it
very clear which enums are supported by the schemas we produce, and adds
very little to no extra boilerplate on the human-written code we
produced previously.

Note, in the generated enum class, because of our use of the clang-tidy
check for macros, the clang-tidy check needs an exception for these
macros that don't technically follow the coding standard.  This seems
like a reasonable compromise, and in this case, given that nlohmann
doesn't support a non-macro version of this.

One question that arises is what this does to the binary size....  Under
the current compiler optimizations, and with the current best practices,
it leads to an overall increase in binary size of ~1200 bytes for the
enum machinery, then approximately 200 bytes for every call site we
switch over.  We should decide if this nominal increase is reasonable.

Tested: Redfish protocol validator runs with same number of failures as
previously.
Redfish Service Validator passes (one unrelated qemu-specific exception)

Signed-off-by: Ed Tanous &lt;edtanous@google.com&gt;
Change-Id: I7c7ee4db0823f7c57ecaa59620b280b53a46e2c1
</content>
</entry>
</feed>
