Re: [PATCH v3] iscsi_ibft: Fix finding the iBFT under Xen Dom 0

From: Dave Hansen
Date: Fri Jun 09 2023 - 11:32:36 EST

Next message: wsa@xxxxxxxxxx: "Re: [PATCH] i2c: xiic: Don't try to handle more interrupt events after error"
Previous message: Neil Armstrong: "Re: [PATCH 03/18] clk: meson: migrate a1 clock drivers out of hw_onecell_data to drop NR_CLKS"
In reply to: Juergen Gross: "Re: [PATCH v3] iscsi_ibft: Fix finding the iBFT under Xen Dom 0"
Next in thread: Dave Hansen: "Re: [PATCH v3] iscsi_ibft: Fix finding the iBFT under Xen Dom 0"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 6/9/23 08:22, Konrad Rzeszutek Wilk wrote:
> Dave, are you OK with the change in where the reserve call is made?

The move makes logical sense. I'm not 100% confident it won't regress
anything, but the blast radius should be limited to iSCSI. But, yeah,
I'm OK with it.

Next message: wsa@xxxxxxxxxx: "Re: [PATCH] i2c: xiic: Don't try to handle more interrupt events after error"
Previous message: Neil Armstrong: "Re: [PATCH 03/18] clk: meson: migrate a1 clock drivers out of hw_onecell_data to drop NR_CLKS"
In reply to: Juergen Gross: "Re: [PATCH v3] iscsi_ibft: Fix finding the iBFT under Xen Dom 0"
Next in thread: Dave Hansen: "Re: [PATCH v3] iscsi_ibft: Fix finding the iBFT under Xen Dom 0"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]