[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60e6bfa6-4267-4d33-9987-24b87c0d0091@lunn.ch>
Date: Thu, 29 Jan 2026 18:44:33 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Piotr Kwapulinski <piotr.kwapulinski@...el.com>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
dan.carpenter@...aro.org, horms@...nel.org, pmenzel@...gen.mpg.de
Subject: Re: [PATCH iwl-next] ixgbe: e610: remove redundant assignment
> /* Read sync Admin Command response */
> - if ((hicr & IXGBE_PF_HICR_SV)) {
> - for (i = 0; i < IXGBE_ACI_DESC_SIZE_IN_DWORDS; i++) {
> + if ((hicr & IXGBE_PF_HICR_SV))
> + for (i = 0; i < IXGBE_ACI_DESC_SIZE_IN_DWORDS; i++)
> raw_desc[i] = IXGBE_READ_REG(hw, IXGBE_PF_HIDA(i));
> - raw_desc[i] = raw_desc[i];
Did you look through the history? When i see code like this it makes
me want to have an understanding why it exists, since it looks so odd.
Is it a merge conflict resolution gone bad? Is it a typo and there is
a cooked_desc[i] which could be set?
> /* Read async Admin Command response */
> - if ((hicr & IXGBE_PF_HICR_EV) && !(hicr & IXGBE_PF_HICR_C)) {
> - for (i = 0; i < IXGBE_ACI_DESC_SIZE_IN_DWORDS; i++) {
> + if ((hicr & IXGBE_PF_HICR_EV) && !(hicr & IXGBE_PF_HICR_C))
> + for (i = 0; i < IXGBE_ACI_DESC_SIZE_IN_DWORDS; i++)
> raw_desc[i] = IXGBE_READ_REG(hw, IXGBE_PF_HIDA_2(i));
> - raw_desc[i] = raw_desc[i];
and it exists twice. Which makes it even odder....
Andrew
Powered by blists - more mailing lists