From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Christoph Hellwig <hch@lst.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Rasesh Mody <rmody@marvell.com>,
GR-Linux-NIC-Dev@marvell.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net v1 1/1] bnx2: Fix unused data compilation warning
Date: Wed, 12 Mar 2025 18:20:17 +0200 [thread overview]
Message-ID: <Z9G0QU5Ew3FusrJH@smile.fi.intel.com> (raw)
In-Reply-To: <067bd072-eb3f-451a-b1c4-59eae777cf00@samsung.com>
On Tue, Mar 11, 2025 at 01:51:21PM +0100, Marek Szyprowski wrote:
> On 05.03.2025 11:00, Andy Shevchenko wrote:
> > On Tue, Mar 04, 2025 at 08:35:24AM -0800, Jakub Kicinski wrote:
> >> On Tue, 4 Mar 2025 15:41:19 +0200 Andy Shevchenko wrote:
...
> >> I meant something more like (untested):
> > We are starving for the comment from the DMA mapping people.
>
> I'm really sorry for this delay. Just got back to the everyday stuff
> after spending a week in bed recovering from flu...
Oh, I hope you feel much better now!
...
> >> #define DEFINE_DMA_UNMAP_ADDR(ADDR_NAME)
> >> #define DEFINE_DMA_UNMAP_LEN(LEN_NAME)
> >> -#define dma_unmap_addr(PTR, ADDR_NAME) (0)
> >> -#define dma_unmap_addr_set(PTR, ADDR_NAME, VAL) do { } while (0)
> >> -#define dma_unmap_len(PTR, LEN_NAME) (0)
> >> -#define dma_unmap_len_set(PTR, LEN_NAME, VAL) do { } while (0)
> >> +#define dma_unmap_addr(PTR, ADDR_NAME) ({ typeof(PTR) __p __maybe_unused = PTR; 0; )}
> >> +#define dma_unmap_addr_set(PTR, ADDR_NAME, VAL) do { typeof(PTR) __p __maybe_unused = PTR; } while (0)
> >> +#define dma_unmap_len(PTR, LEN_NAME) ({ typeof(PTR) __p __maybe_unused = PTR; 0; )}
> >> +#define dma_unmap_len_set(PTR, LEN_NAME, VAL) do { typeof(PTR) __p __maybe_unused = PTR; } while (0)
> >> I just don't know how much code out there depends on PTR not
> >> existing if !CONFIG_NEED_DMA_MAP_STATE
> > Brief checking shows that only drivers/net/ethernet/chelsio/* comes
> > with ifdeffery, the rest most likely will fail in the same way
> > (note, overwhelming majority of the users is under the network realm):
>
> Frankly speaking I wasn't aware of this API till now.
>
> If got it right the above proposal should work fine. The addr/len names
> can be optimized out, but the pointer to the container should exist.
Thanks for the reply, would you or Jakub will to send a formal patch?
I can test it on my configuration and build.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-03-12 16:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 10:05 [PATCH net v1 1/1] bnx2: Fix unused data compilation warning Andy Shevchenko
2025-03-04 1:21 ` Jakub Kicinski
2025-03-04 10:56 ` Andy Shevchenko
2025-03-04 11:39 ` Paolo Abeni
2025-03-04 11:58 ` Andy Shevchenko
2025-03-04 13:41 ` Andy Shevchenko
2025-03-04 16:35 ` Jakub Kicinski
2025-03-05 10:00 ` Andy Shevchenko
2025-03-11 12:51 ` Marek Szyprowski
2025-03-12 16:20 ` Andy Shevchenko [this message]
2025-04-14 10:08 ` Andy Shevchenko
2025-04-15 9:43 ` Andy Shevchenko
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=Z9G0QU5Ew3FusrJH@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmody@marvell.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.