From: Simon Horman <simon.horman@corigine.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org, magnus.karlsson@intel.com,
przemyslaw.kitszel@intel.com
Subject: Re: [Intel-wired-lan] [PATCH v2 iwl-next] ice: use ice_down_up() where applicable
Date: Wed, 14 Jun 2023 10:06:10 +0200 [thread overview]
Message-ID: <ZIl08oBdRZa3RG10@corigine.com> (raw)
In-Reply-To: <20230613113552.336520-1-maciej.fijalkowski@intel.com>
On Tue, Jun 13, 2023 at 01:35:52PM +0200, Maciej Fijalkowski wrote:
> ice_change_mtu() is currently using a separate ice_down() and ice_up()
> calls to reflect changed MTU. ice_down_up() serves this purpose, so do
> the refactoring here.
>
> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <simon.horman@corigine.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, magnus.karlsson@intel.com,
przemyslaw.kitszel@intel.com
Subject: Re: [PATCH v2 iwl-next] ice: use ice_down_up() where applicable
Date: Wed, 14 Jun 2023 10:06:10 +0200 [thread overview]
Message-ID: <ZIl08oBdRZa3RG10@corigine.com> (raw)
In-Reply-To: <20230613113552.336520-1-maciej.fijalkowski@intel.com>
On Tue, Jun 13, 2023 at 01:35:52PM +0200, Maciej Fijalkowski wrote:
> ice_change_mtu() is currently using a separate ice_down() and ice_up()
> calls to reflect changed MTU. ice_down_up() serves this purpose, so do
> the refactoring here.
>
> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-06-14 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 11:35 [Intel-wired-lan] [PATCH v2 iwl-next] ice: use ice_down_up() where applicable Maciej Fijalkowski
2023-06-13 11:35 ` Maciej Fijalkowski
2023-06-13 11:42 ` [Intel-wired-lan] " Przemek Kitszel
2023-06-13 11:42 ` Przemek Kitszel
2023-06-14 8:06 ` Simon Horman [this message]
2023-06-14 8:06 ` Simon Horman
2023-06-19 4:44 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-06-19 4:44 ` Pucha, HimasekharX Reddy
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=ZIl08oBdRZa3RG10@corigine.com \
--to=simon.horman@corigine.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.