From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
larysa.zaremba@intel.com, kalesh-anakkur.purayil@broadcom.com,
Jakub Kicinski <kuba@kernel.org>,
Igor Bagnucki <igor.bagnucki@intel.com>
Subject: Re: [PATCH iwl-net v4] ice: Add netif_device_attach/detach into PF reset flow
Date: Wed, 21 Aug 2024 10:10:21 +0200 [thread overview]
Message-ID: <25c69f6d-bd04-429e-a1d5-c6985b6555bf@linux.intel.com> (raw)
In-Reply-To: <ZsWHsaUbYo9Qb6v2@boxer>
On 21.08.2024 08:22, Maciej Fijalkowski wrote:
> On Tue, Aug 20, 2024 at 06:15:24PM +0200, Dawid Osuchowski wrote:
>> @@ -7591,6 +7594,7 @@ static void ice_rebuild(struct ice_pf *pf, enum ice_reset_req reset_type)
>> {
>> struct device *dev = ice_pf_to_dev(pf);
>> struct ice_hw *hw = &pf->hw;
>> + struct ice_vsi *vsi = ice_get_main_vsi(pf);
>
> we have an unwritten rule that is called 'reverse christmas tree' which
> requires us to have declarations of variables sorted from longest to
> shortest.
>
> struct ice_vsi *vsi = ice_get_main_vsi(pf);
> struct device *dev = ice_pf_to_dev(pf);
> struct ice_hw *hw = &pf->hw;
> bool dvm;
> int err;
>
My apologies, I was not aware of that unwritten rule. Will fix in next
revision, thanks. Other than that, does the rest of the changes look
okay to you?
--Dawid
next prev parent reply other threads:[~2024-08-21 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 16:15 [PATCH iwl-net v4] ice: Add netif_device_attach/detach into PF reset flow Dawid Osuchowski
2024-08-21 6:22 ` Maciej Fijalkowski
2024-08-21 8:10 ` Dawid Osuchowski [this message]
2024-08-21 8:43 ` Przemek Kitszel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25c69f6d-bd04-429e-a1d5-c6985b6555bf@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=igor.bagnucki@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).