On 1/16/19 7:35 AM, Sasha Levin wrote:

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v4.20.2, v4.19.15, v4.14.93, v4.9.150, v4.4.170, v3.18.132.

I'll pull these into my tree.

It sounds like you want this in ASAP, I can do that, though this interface is lower priority, I would think, because it's generally root access only.

-corey

v4.20.2: Build OK! v4.19.15: Build OK! v4.14.93: Failed to apply! Possible dependencies: 1c9f98d1bfbd ("ipmi: Make IPMI panic strings always available") 3fd32f9ec84f ("ipmi: Convert IPMI GUID over to Linux guid_t") 511d57dc71a2 ("ipmi: Get the device id through a function") 68e7e50f195f ("ipmi: Don't use BMC product/dev ids in the BMC name") 9ca15af3164f ("ipmi: Fix issues with BMC refcounts") a2cb600fa22a ("ipmi: Rework BMC registration") a9137c3dfae9 ("ipmi: Add a reference from BMC devices to their interfaces") aa9c9ab2443e ("ipmi: allow dynamic BMC version information") b2cfd8ab4add ("ipmi: Rework device id and guid handling to catch changing BMCs") c0734bd594d4 ("ipmi: Retry BMC registration on a failure") f33e4df83e00 ("ipmi: Move bmc find routing to below bmc device type")

v4.9.150: Failed to apply! Possible dependencies: 1c9f98d1bfbd ("ipmi: Make IPMI panic strings always available") 3fd32f9ec84f ("ipmi: Convert IPMI GUID over to Linux guid_t") 511d57dc71a2 ("ipmi: Get the device id through a function") 68e7e50f195f ("ipmi: Don't use BMC product/dev ids in the BMC name") 9ca15af3164f ("ipmi: Fix issues with BMC refcounts") a2cb600fa22a ("ipmi: Rework BMC registration") a9137c3dfae9 ("ipmi: Add a reference from BMC devices to their interfaces") aa9c9ab2443e ("ipmi: allow dynamic BMC version information") b2cfd8ab4add ("ipmi: Rework device id and guid handling to catch changing BMCs") c0734bd594d4 ("ipmi: Retry BMC registration on a failure") f33e4df83e00 ("ipmi: Move bmc find routing to below bmc device type")

v4.4.170: Failed to apply! Possible dependencies: 1c9f98d1bfbd ("ipmi: Make IPMI panic strings always available") 3fd32f9ec84f ("ipmi: Convert IPMI GUID over to Linux guid_t") 511d57dc71a2 ("ipmi: Get the device id through a function") 68e7e50f195f ("ipmi: Don't use BMC product/dev ids in the BMC name") 9ca15af3164f ("ipmi: Fix issues with BMC refcounts") a2cb600fa22a ("ipmi: Rework BMC registration") a9137c3dfae9 ("ipmi: Add a reference from BMC devices to their interfaces") aa9c9ab2443e ("ipmi: allow dynamic BMC version information") b2cfd8ab4add ("ipmi: Rework device id and guid handling to catch changing BMCs") bd85f4b37ddf ("ipmi: fix crash on reading version from proc after unregisted bmc") c0734bd594d4 ("ipmi: Retry BMC registration on a failure") f33e4df83e00 ("ipmi: Move bmc find routing to below bmc device type")

v3.18.132: Failed to apply! Possible dependencies: 16639eb08a69 ("ipmi: clean up the device handling for the bmc device") 1c9f98d1bfbd ("ipmi: Make IPMI panic strings always available") 3fd32f9ec84f ("ipmi: Convert IPMI GUID over to Linux guid_t") 5a0e10ec4a82 ("ipmi: Remove useless sysfs_name parameters") 9ca15af3164f ("ipmi: Fix issues with BMC refcounts") a2cb600fa22a ("ipmi: Rework BMC registration") a9137c3dfae9 ("ipmi: Add a reference from BMC devices to their interfaces") aa9c9ab2443e ("ipmi: allow dynamic BMC version information") b2cfd8ab4add ("ipmi: Rework device id and guid handling to catch changing BMCs") bd85f4b37ddf ("ipmi: fix crash on reading version from proc after unregisted bmc") c0734bd594d4 ("ipmi: Retry BMC registration on a failure") f33e4df83e00 ("ipmi: Move bmc find routing to below bmc device type")

How should we proceed with this patch?

-- Thanks, Sasha