From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org, magnus.karlsson@intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 2/3] ice: avoid unnecessary devm_ usage
Date: Fri, 23 Feb 2024 16:03:02 +0100 [thread overview]
Message-ID: <Zdizphq09RItsiaA@boxer> (raw)
In-Reply-To: <b50229cb-e3b0-44f8-9725-6592b74dfebf@intel.com>
On Fri, Feb 23, 2024 at 08:45:20AM +0100, Przemek Kitszel wrote:
> On 2/22/24 15:50, Maciej Fijalkowski wrote:
> > 1. pcaps are free'd right after AQ routines are done, no need for
> > devm_'s
> > 2. a test frame for loopback test in ethtool -t is destroyed at the end
> > of the test so we don't need devm_ here either.
> >
> > Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> > ---
> > drivers/net/ethernet/intel/ice/ice_common.c | 23 +++++++++-----------
> > drivers/net/ethernet/intel/ice/ice_ethtool.c | 4 ++--
> > 2 files changed, 12 insertions(+), 15 deletions(-)
> >
>
> nice, thank you!
>
> BTW, we are committed to using Scope Based Resource Management [1] even
> in the OOT driver, so you could consider that for future IWL submissions
> :)
Thanks for reminding me about this, will do that.
>
> [1] https://lwn.net/Articles/934679/
>
>
> I'm also happy with this as-is too, so:
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<anthony.l.nguyen@intel.com>, <magnus.karlsson@intel.com>
Subject: Re: [PATCH iwl-next 2/3] ice: avoid unnecessary devm_ usage
Date: Fri, 23 Feb 2024 16:03:02 +0100 [thread overview]
Message-ID: <Zdizphq09RItsiaA@boxer> (raw)
In-Reply-To: <b50229cb-e3b0-44f8-9725-6592b74dfebf@intel.com>
On Fri, Feb 23, 2024 at 08:45:20AM +0100, Przemek Kitszel wrote:
> On 2/22/24 15:50, Maciej Fijalkowski wrote:
> > 1. pcaps are free'd right after AQ routines are done, no need for
> > devm_'s
> > 2. a test frame for loopback test in ethtool -t is destroyed at the end
> > of the test so we don't need devm_ here either.
> >
> > Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> > ---
> > drivers/net/ethernet/intel/ice/ice_common.c | 23 +++++++++-----------
> > drivers/net/ethernet/intel/ice/ice_ethtool.c | 4 ++--
> > 2 files changed, 12 insertions(+), 15 deletions(-)
> >
>
> nice, thank you!
>
> BTW, we are committed to using Scope Based Resource Management [1] even
> in the OOT driver, so you could consider that for future IWL submissions
> :)
Thanks for reminding me about this, will do that.
>
> [1] https://lwn.net/Articles/934679/
>
>
> I'm also happy with this as-is too, so:
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
next prev parent reply other threads:[~2024-02-23 15:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 14:50 [Intel-wired-lan] [PATCH iwl-next 0/3] intel: misc improvements Maciej Fijalkowski
2024-02-22 14:50 ` Maciej Fijalkowski
2024-02-22 14:50 ` [Intel-wired-lan] [PATCH iwl-next 1/3] ice: do not disable Tx queues twice in ice_down() Maciej Fijalkowski
2024-02-22 14:50 ` Maciej Fijalkowski
2024-02-22 14:50 ` [Intel-wired-lan] [PATCH iwl-next 2/3] ice: avoid unnecessary devm_ usage Maciej Fijalkowski
2024-02-22 14:50 ` Maciej Fijalkowski
2024-02-23 7:45 ` [Intel-wired-lan] " Przemek Kitszel
2024-02-23 7:45 ` Przemek Kitszel
2024-02-23 15:03 ` Maciej Fijalkowski [this message]
2024-02-23 15:03 ` Maciej Fijalkowski
2024-02-23 9:35 ` [Intel-wired-lan] " kernel test robot
2024-02-23 9:35 ` kernel test robot
2024-02-22 14:50 ` [Intel-wired-lan] [PATCH iwl-next 3/3] ixgbe: pull out stats update to common routines Maciej Fijalkowski
2024-02-22 14:50 ` Maciej Fijalkowski
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=Zdizphq09RItsiaA@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--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.