From: Thorsten Blum <thorsten.blum@toblux.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Nicolas Pitre" <nico@fluxnic.net>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Breno Leitao" <leitao@debian.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Andrew Lunn" <andrew@lunn.ch>,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"Arnd Bergmann" <arnd@arndb.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: smc91x: Refactor SMC_* macros
Date: Thu, 30 May 2024 03:53:00 +0200 [thread overview]
Message-ID: <A004D09E-E9CC-4DD4-ADE7-791D63D962D3@toblux.com> (raw)
In-Reply-To: <20240529171740.0643a5a1@kernel.org>
On 30. May 2024, at 02:17, Jakub Kicinski <kuba@kernel.org> wrote:
> On Tue, 28 May 2024 12:44:23 +0200 Thorsten Blum wrote:
>> Use the macro parameter lp directly instead of relying on ioaddr being
>> defined in the surrounding scope.
>
> Have you tested this, or just compile tested (please mention what
> testing has been done in the commit message in the future)?
Just compile tested.
> What's the motivation - cleanup or this helps remove some warnings?
> (again, please mention in the commit message)
It's a cleanup suggested by Andrew Lunn [1][2]. His suggestion might
have been for SMC_PUSH_DATA() and SMC_PULL_DATA() only; or to add
another macro param for ioaddr if lp->base and ioaddr are different (as
in smc_probe()).
> AFAICT this will break smc_probe().
Yes, it does break smc_probe(). I'll fix it and submit a v2.
Thanks,
Thorsten
[1] https://lore.kernel.org/linux-kernel/0efd687d-3df5-49dd-b01c-d5bd977ae12e@lunn.ch/
[2] https://lore.kernel.org/linux-kernel/f192113c-9aee-47be-85f6-cd19fcb81a5e@lunn.ch/
prev parent reply other threads:[~2024-05-30 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 10:44 Thorsten Blum
2024-05-28 12:08 ` Andrew Lunn
2024-05-30 0:17 ` Jakub Kicinski
2024-05-30 1:53 ` Thorsten Blum [this message]
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=A004D09E-E9CC-4DD4-ADE7-791D63D962D3@toblux.com \
--to=thorsten.blum@toblux.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=pabeni@redhat.com \
--cc=u.kleine-koenig@pengutronix.de \
/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
all inboxes | Powered by JetHome®