From: "Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
To: "Lobakin, Alexandr" <alexandr.lobakin@intel.com>,
"christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH] intel: Simplify DMA setting
Date: Tue, 4 Jan 2022 21:56:03 +0000 [thread overview]
Message-ID: <c258c3bb440b88e984b0385af8ffb38a017ba644.camel@intel.com> (raw)
In-Reply-To: <20220104132936.252202-1-alexandr.lobakin@intel.com>
On Tue, 2022-01-04 at 14:29 +0100, Alexander Lobakin wrote:
> From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> Date: Tue, 4 Jan 2022 01:15:20 +0100
>
> > As stated in [1], dma_set_mask() with a 64-bit mask will never fail
> > if
> > dev->dma_mask is non-NULL.
> > So, if it fails, the 32 bits case will also fail for the same
> > reason.
> >
> > Simplify code and remove some dead code accordingly.
> >
> > [1]: https://lkml.org/lkml/2021/6/7/398
> >
> > Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> > ---
> > drivers/net/ethernet/intel/e1000e/netdev.c | 22 ++++++---------
> > ----
> > drivers/net/ethernet/intel/i40e/i40e_main.c | 9 +++-----
> > drivers/net/ethernet/intel/iavf/iavf_main.c | 9 +++-----
> > drivers/net/ethernet/intel/ice/ice_main.c | 2 --
> > drivers/net/ethernet/intel/ixgb/ixgb_main.c | 19 +++++----------
> > -
> > drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 20 ++++++---------
> > --
> > .../net/ethernet/intel/ixgbevf/ixgbevf_main.c | 20 +++++----------
> > --
> > 7 files changed, 31 insertions(+), 70 deletions(-)
>
> I like it, thanks!
>
> Reviewed-by: Alexander Lobakin <alexandr.lobakin@intel.com>
>
> Tony might ask to split it into per-driver patches tho, will see.
Hi Christophe,
As mentioned by others, would mind breaking these per-driver?
Thanks,
Tony
>
> --- 8< ---
>
> Al
next prev parent reply other threads:[~2022-01-04 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 0:15 [PATCH] intel: Simplify DMA setting Christophe JAILLET
2022-01-04 7:53 ` Christoph Hellwig
2022-01-04 13:29 ` [Intel-wired-lan] " Alexander Lobakin
2022-01-04 21:56 ` Nguyen, Anthony L [this message]
2022-01-05 6:31 ` Christophe JAILLET
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=c258c3bb440b88e984b0385af8ffb38a017ba644.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=alexandr.lobakin@intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).