<feed xmlns='http://www.w3.org/2005/Atom'>
<title>BMC/OpenBmc/bmcweb.git/meson.options, 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-07-24T17:31:51+00:00</updated>
<entry>
<title>Add Fuzz target</title>
<updated>2026-07-24T17:31:51+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>etanous@nvidia.com</email>
</author>
<published>2026-04-24T18:06:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=e05fbc05005db284f418f8517d215c97b9b189f4'/>
<id>urn:sha1:e05fbc05005db284f418f8517d215c97b9b189f4</id>
<content type='text'>
Recently, oss-fuzz added support for bmcweb, but did it by checking in
a number of code patches.  This commit should get similar coverage by
hooking into the HTTP connection class, and using the unit test
code to inject bytes directly into a stream.  This can be improved over
time, but this is a good start.

Change-Id: I20b5d536cff1588a8387f2770c022516e1cd62d0
Signed-off-by: Ed Tanous &lt;etanous@nvidia.com&gt;
</content>
</entry>
<entry>
<title>Change cipher suite defaults to modern</title>
<updated>2026-07-07T23:03:22+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>etanous@nvidia.com</email>
</author>
<published>2026-06-12T18:47:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=37b599b8693994749d37d663950392650748643e'/>
<id>urn:sha1:37b599b8693994749d37d663950392650748643e</id>
<content type='text'>
This commit changes the defaults to using Mozilla modern
recommendations, and disables TLS1.2 support.  This should be a noop for
almost all uses, as any modern OS has had support for this cipher suite
for a very long time.  Mozilla intermediate is added still as a compile
time fallback in case some clients are impacted, but expectation is that
this is only a security increase for any client new enough to be worth
caring about.[1]

Tested:

Ran testssl.sh, and verified that the appropriate cipher suites and TLS
versions reported.

[1] https://caniuse.com/tls1-3

Change-Id: I31e51fabaa08e01d095035896a59b375b2e336f0
Signed-off-by: Ed Tanous &lt;etanous@nvidia.com&gt;
</content>
</entry>
<entry>
<title>Allow setting Mozilla modern</title>
<updated>2026-07-02T18:30:22+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>etanous@nvidia.com</email>
</author>
<published>2026-05-26T20:28:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=917fbad478cf5db4a79944d59a4927207adf49d1'/>
<id>urn:sha1:917fbad478cf5db4a79944d59a4927207adf49d1</id>
<content type='text'>
Mozilla publishes recommendations for TLS cipher suites to support.  For
many years bmcweb selected "intermediate" because of compatibility with
clients that didn't yet support TLS1.3.

This commit adds the ability to use the Mozilla modern recommendations,
and disable TLS1.2 support through a new meson option, tls-profile.

Tested:

Loaded on qemu, and verified with testssl.sh[1] that parameters were
applied.

[1] https://github.com/testssl/testssl.sh

Change-Id: I38e915b3943b5dbe5fb31e54eb3ebda9bbaeb811
Signed-off-by: Ed Tanous &lt;etanous@nvidia.com&gt;
</content>
</entry>
<entry>
<title>meson: fix typo in comment (leiu -&gt; lieu)</title>
<updated>2026-06-26T19:59:57+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2026-05-18T20:07:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=969403086e314f06b65a54ed90ccd548ea996901'/>
<id>urn:sha1:969403086e314f06b65a54ed90ccd548ea996901</id>
<content type='text'>
Change-Id: I29a0428bc86606350957072bcd02d587cea8d503
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>meson: fix extra period in description</title>
<updated>2026-06-26T19:59:57+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2026-06-26T17:03:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=99548d0f84c1de3bd80639aa8a513740016584c6'/>
<id>urn:sha1:99548d0f84c1de3bd80639aa8a513740016584c6</id>
<content type='text'>
Change-Id: I84134ec905d8b9386e89d27d07675b720e8f87f2
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Bump expiry of experimental-multi-computer-system</title>
<updated>2026-06-17T17:07:56+00:00</updated>
<author>
<name>Oliver Brewka</name>
<email>oliver.brewka@9elements.com</email>
</author>
<published>2026-06-17T17:06:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=475c0320df87786a8e2a089544b52a316bd54819'/>
<id>urn:sha1:475c0320df87786a8e2a089544b52a316bd54819</id>
<content type='text'>
Bump expiry to 1/1/2027

Change-Id: I193b9a69aba6134b6add0816bf67640f073bef82
Signed-off-by: Oliver Brewka &lt;oliver.brewka@9elements.com&gt;
</content>
</entry>
<entry>
<title>HTTP/2: Reject over limit Content-Length</title>
<updated>2026-04-21T17:31:11+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2026-02-26T23:14:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=62526bb070f784fa4ae92b3e742bded00e78f40a'/>
<id>urn:sha1:62526bb070f784fa4ae92b3e742bded00e78f40a</id>
<content type='text'>
Reject requests whose Content-Length exceeds BMCWEB_HTTP_BODY_LIMIT
before calling reserve().

BMCWEB_HTTP_BODY_LIMIT is defaulted to 30 Mebibyte (MiB). Make the unit
clear in the meson.option too.

Tested: See the trace. The reserve doesn't happen. Not sending a
RST_STREAM / 413 based on how init() works today. WIP.

Change-Id: Ie1e0ba19e2999c2f6c9e18f2b98e49c4bd100bcc
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Fix spelling mistakes using codespell</title>
<updated>2026-02-24T18:30:31+00:00</updated>
<author>
<name>George Liu</name>
<email>liuxiwei@ieisystem.com</email>
</author>
<published>2026-02-24T02:31:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=8f04d1710bb90a9dd225ce9b82cb0c157460b4a4'/>
<id>urn:sha1:8f04d1710bb90a9dd225ce9b82cb0c157460b4a4</id>
<content type='text'>
Signed-off-by: George Liu &lt;liuxiwei@ieisystem.com&gt;
Change-Id: If170e53077bc150d0062cd441394daea71f842b1
</content>
</entry>
<entry>
<title>Sensors: Convert fan_tach sensors to Percent</title>
<updated>2026-02-05T20:17:04+00:00</updated>
<author>
<name>Janet Adkins</name>
<email>janeta@us.ibm.com</email>
</author>
<published>2025-10-29T21:49:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=433c9193b0d086f009d53a5860f1ee586cf45792'/>
<id>urn:sha1:433c9193b0d086f009d53a5860f1ee586cf45792</id>
<content type='text'>
Redfish 2025.3 clarified the reporting of fan sensors should always be
as ReadingType Percent to address issue #6197. [1] The fan_tach
sensors on D-Bus are Rotational sensors. Conversion is necessary for
these sensor values to reflect Percent instead. [2] This is reflected in
a published mockup. [3]

The Redfish update includes an additional sentence for the ReadingType
description:

```
"... Services should represent fan speed and pump speed sensors with the `ReadingType` value `Percent`."
```

The ReadingRangeMax and ReadingRangeMin properties also must be
converted to percent basis as they are defined to reflect the range of
the Reading property.

```
curl -s https://redfish.dmtf.org/schemas/v1/Sensor.v1_11_1.json | jq .definitions.Sensor.properties.ReadingRangeMax.longDescription
"This property shall indicate the maximum possible value of the `Reading` property for this sensor.  This value is the range of valid readings for this sensor.  Values outside this range are discarded as reading errors."
```

A new compile option, redfish-allow-rotational-fans, will maintain the
old behavior of reporting fan_tach sensors as Rotational. When the
option is disabled they will be reported as Percent. This will allow
time for distributions to make adjustments to handle Percent reported
fan sensors.

The SpeedRPM Redfish property contains the RPM value for these sensors
whether this option is enabled or disabled. Clients wanting to use the
RPM value should convert to use the SpeedRPM property instead of the
Reading property.

```
curl -s https://redfish.dmtf.org/schemas/v1/Sensor.v1_11_1.json | jq .definitions.Sensor.properties.SpeedRPM
{
  "description": "The rotational speed.",
  "excerpt": "SensorFan,SensorFanArray,SensorPump",
  "longDescription": "This property shall contain a reading of the rotational speed of the device in revolutions per minute (RPM) units.",
  "readonly": true,
  "type": [
    "number",
    "null"
  ],
  "units": "{rev}/min",
  "versionAdded": "v1_2_0"
}
```

With the compile option disabled the following differences will be
reflected in the responses for /redfish/v1/Chassis/chassis/Sensors/{}:
 - ReadingRangeMax/ReadingRangeMin: Converted to percent range, (100,0)
 - ReadingType: "Percent"
 - ReadingUnits: "%"
 - Reading: Computed percent value. The computation is the percent of
   the RPM Value within the MaxValue to MinValue range as reported by
   D-Bus for the sensor.
 - Note: If the percent cannot be computed for any reason the Reading
   property is set to null.
 - Note: SpeedRPM: Remains unchanged, it continues to report the RPM
   value as reported by D-Bus.

Implementation Notes:
 - The SensorFanExcerpt and SensorFanArrayExcerpt definitions also
   include the SpeedRPM property. So moved setting of this property to
   be handled for excerpts as well.
 - The Sensor schema version has been updated regardless of the compile
   option setting.

[1] https://github.com/DMTF/Redfish/issues/6197
[2] https://redfish.dmtf.org/schemas/v1/Sensor.v1_11_1.json
[3] https://github.com/DMTF/Redfish-Publications/blob/main/mockups/public-rackmount1/Chassis/1U/Sensors/CPUFan1/index.json

Tested:
 - Added new unit tests for new function getFanPercent()
 - Adjusted existing unit tests for Sensors to reflect changes for
   fan_tach sensors.
 - Redfish Service Validator passes (with option enabled and disabled)
 - Using hardware simulator hand-edited values for the min/max of the
   fan_tach sensors:
   - Option enabled: confirmed Redfish response same before and after
     code changes.
   - Option disabled: Confirmed Redfish responses and percent
     calculation.

Example responses with compile option disabled:
```
// D-Bus:  "Value" d 18000 "MaxValue" d 18000 "MinValue" d 0
curl -s -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassis/Sensors/fantach_fan0_0
{
  "@odata.id": "/redfish/v1/Chassis/chassis/Sensors/fantach_fan0_0",
  "@odata.type": "#Sensor.v1_11_1.Sensor",
  "Id": "fantach_fan0_0",
  "Name": "fan0 0",
  "Reading": 100,
  "ReadingRangeMax": 100,
  "ReadingRangeMin": 0,
  "ReadingType": "Percent",
  "ReadingUnits": "%",
  "SpeedRPM": 18000.0,
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}

// D-Bus: "Value" d 18000 "MaxValue" d 36000 "MinValue" d 0
curl -s -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassis/Sensors/fantach_fan1_0
{
  "@odata.id": "/redfish/v1/Chassis/chassis/Sensors/fantach_fan1_0",
  "@odata.type": "#Sensor.v1_11_1.Sensor",
  "Id": "fantach_fan1_0",
  "Name": "fan1 0",
  "Reading": 50,
  "ReadingRangeMax": 100,
  "ReadingRangeMin": 0,
  "ReadingType": "Percent",
  "ReadingUnits": "%",
  "SpeedRPM": 18000.0,
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}

// Minimum is non-zero
// D-Bus: "Value" d 18000 "MaxValue" d 27000 "MinValue" d 9000
curl -s -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassis/Sensors/fantach_fan2_0
{
  "@odata.id": "/redfish/v1/Chassis/chassis/Sensors/fantach_fan2_0",
  "@odata.type": "#Sensor.v1_11_1.Sensor",
  "Id": "fantach_fan2_0",
  "Name": "fan2 0",
  "Reading": 50,
  "ReadingRangeMax": 100,
  "ReadingRangeMin": 0,
  "ReadingType": "Percent",
  "ReadingUnits": "%",
  "SpeedRPM": 18000.0,
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}

// Minimum is not initialized - Reading is null
// D-Bus: "Value" d 18000 "MaxValue" d 18000 "MinValue" d -inf
curl -s -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassis/Sensors/fantach_fan3_0
{
  "@odata.id": "/redfish/v1/Chassis/chassis/Sensors/fantach_fan3_0",
  "@odata.type": "#Sensor.v1_11_1.Sensor",
  "Id": "fantach_fan3_0",
  "Name": "fan3 0",
  "Reading": null,
  "ReadingRangeMax": 100,
  "ReadingRangeMin": 0,
  "ReadingType": "Percent",
  "ReadingUnits": "%",
  "SpeedRPM": 18000.0,
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}

// Minimum and Maximum are not initialized - so Reading is null
// D-Bus: "Value" d 18000 "MaxValue" d inf "MinValue" d -inf
curl -s -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassis/Sensors/fantach_fan4_0
{
  "@odata.id": "/redfish/v1/Chassis/chassis/Sensors/fantach_fan4_0",
  "@odata.type": "#Sensor.v1_11_1.Sensor",
  "Id": "fantach_fan4_0",
  "Name": "fan4 0",
  "Reading": null,
  "ReadingRangeMax": 100,
  "ReadingRangeMin": 0,
  "ReadingType": "Percent",
  "ReadingUnits": "%",
  "SpeedRPM": 18000.0,
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}
```

Example of unchanged response with compile option enabled:
```
curl -s -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassis/Sensors/fantach_fan0_0
{
  "@odata.id": "/redfish/v1/Chassis/chassis/Sensors/fantach_fan0_0",
  "@odata.type": "#Sensor.v1_11_1.Sensor",
  "Id": "fantach_fan0_0",
  "Name": "fan0 0",
  "Reading": 18000.0,
  "ReadingRangeMax": 18000.0,
  "ReadingRangeMin": 0.0,
  "ReadingType": "Rotational",
  "ReadingUnits": "RPM",
  "SpeedRPM": 18000.0,
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}
```

Change-Id: I8ec1e739bcd5ebce7453a2570569f2edc2284341
Signed-off-by: Janet Adkins &lt;janeta@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Fabric: add support for PCIe Switch Port URI</title>
<updated>2026-02-03T17:24:36+00:00</updated>
<author>
<name>Harshit Aghera</name>
<email>haghera@nvidia.com</email>
</author>
<published>2025-10-07T08:28:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/BMC/OpenBmc/bmcweb.git/commit/?id=3132dacead062fa63c070fc7f404f8cf93df43a0'/>
<id>urn:sha1:3132dacead062fa63c070fc7f404f8cf93df43a0</id>
<content type='text'>
This patch enable support for following properties for Port of a PCIe
Switch. [1]
- PortProtocol
- PortType
- CurrentSpeedGbps
- ActiveWidth

One of the devices that gets enabled with this patch is Nvidia ConnectX
devices, which are network cards featuring an integrated PCIe switch.
These devices combine both PCIe ports and network ports in a single
unit. Since such devices don't strictly qualify as Fabric Adapters, the
Switch URI is used instead of the FabricAdapter URI.

Port schema only allows certain URIs as Port URI. URI
/redfish/v1/Fabrics/{FabricId}/Switches/{SwitchId}/Ports/{PortId} seems
most appropriate choice for PCIe Switch Port. [1]

The Fabric resource is modeled similarly to the System resource, meaning
that only one Fabric resource will exist for each BMC. Route handler for
collections and each individual components are added in this patch for
each URI resource under /redfish/v1/Fabrics.

DBus Interface "xyz.openbmc_project.Inventory.Item.PCIeSwitch" is used
to identify the Switch resources. Association between Switch and Port is
`connecting` and `connected_to`.

Feature like Port Metrics properties (for PCIe Error Counters) can be
added in future at Port Metric URI.

dbus-sensors patches -
https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/84079
https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/83202

Tested: Build an image for nvl32-obmc machine with the following patch
cherry picked.

https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/84079
https://gerrit.openbmc.org/c/openbmc/openbmc/+/85490

The openbmc patch cherry-picks the following patches that are currently
under review.

```
1. device tree
https://lore.kernel.org/all/aRbLqH8pLWCQryhu@molberding.nvidia.com/
2. mctpd patches
https://github.com/CodeConstruct/mctp/pull/85
3. u-boot changes
https://lore.kernel.org/openbmc/20251121-msx4-v1-0-fc0118b666c1@nvidia.com/T/#t
4. kernel changes as specified in the openbmc patch (for espi)
5. entity-manager changes
https://gerrit.openbmc.org/c/openbmc/entity-manager/+/85455
6. platform-init changes
https://gerrit.openbmc.org/c/openbmc/platform-init/+/85456
7. spi changes
https://lore.kernel.org/all/20251121-w25q01jv_fixup-v1-1-3d175050db73@nvidia.com/
```

redfish service validator is passing.

```
$ curl -k -u 'root:0penBmc' https://${bmc_ip}/redfish/v1/Fabrics/
{
  "@odata.id": "/redfish/v1/Fabrics",
  "@odata.type": "#FabricCollection.FabricCollection",
  "Members": [
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric"
    }
  ],
  "Members@odata.count": 1,
  "Name": "Fabric Collection"
}%

$ curl -k -u 'root:0penBmc' https://${bmc_ip}/redfish/v1/Fabrics/fabric/
{
  "@odata.id": "/redfish/v1/Fabrics/fabric",
  "@odata.type": "#Fabric.v1_2_0.Fabric",
  "Id": "fabric",
  "Name": "fabric Fabric",
  "Switches": {
    "@odata.id": "/redfish/v1/Fabrics/fabric/Switches"
  }
}%

$ curl -k -u 'root:0penBmc' https://${bmc_ip}/redfish/v1/Fabrics/fabric/Switches/
{
  "@odata.id": "/redfish/v1/Fabrics/fabric/Switches",
  "@odata.type": "#SwitchCollection.SwitchCollection",
  "Members": [
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0"
    },
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_1"
    },
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_2"
    },
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_3"
    }
  ],
  "Members@odata.count": 4,
  "Name": "fabric Switch Collection"
}%

$ curl -k -u 'root:0penBmc' https://${bmc_ip}/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0
{
  "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0",
  "@odata.type": "#Switch.v1_7_0.Switch",
  "Id": "Nvidia_ConnectX_0",
  "Name": "Nvidia_ConnectX_0",
  "Ports": {
    "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports"
  },
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}%

$ curl -k -u 'root:0penBmc' https://${bmc_ip}/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports/
{
  "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports",
  "@odata.type": "#PortCollection.PortCollection",
  "Members": [
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports/DOWN_0"
    },
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports/DOWN_1"
    },
    {
      "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports/UP_0"
    }
  ],
  "Members@odata.count": 3,
  "Name": "Nvidia_ConnectX_0 Port Collection"
}%

$ curl -k -u 'root:0penBmc' https://${bmc_ip}/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports/UP_0/
{
  "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports/UP_0",
  "@odata.type": "#Port.v1_4_0.Port",
  "ActiveWidth": 8,
  "CurrentSpeedGbps": 32.0,
  "Id": "UP_0",
  "Metrics": {
    "@odata.id": "/redfish/v1/Fabrics/fabric/Switches/Nvidia_ConnectX_0/Ports/UP_0/Metrics"
  },
  "Name": "Nvidia_ConnectX_0 UP_0 Port",
  "PortProtocol": "PCIe",
  "PortType": "UpstreamPort",
  "Status": {
    "Health": "OK",
    "State": "Enabled"
  }
}%
```

[1]: https://redfish.dmtf.org/schemas/v1/Port_v1.xml

Change-Id: I52f4ca62b4953f6196c589e340602a0d7885d9c1
Signed-off-by: Harshit Aghera &lt;haghera@nvidia.com&gt;
</content>
</entry>
</feed>
