From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Rosen Penev <rosenp@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org, p.zabel@pengutronix.de
Subject: Re: [PATCH net-next 3/6] net: ag71xx: use ethtool_puts
Date: Fri, 30 Aug 2024 06:55:23 +0200 [thread overview]
Message-ID: <ZtFQu777F8bSijGD@pengutronix.de> (raw)
In-Reply-To: <20240829214838.2235031-4-rosenp@gmail.com>
On Thu, Aug 29, 2024 at 02:48:22PM -0700, Rosen Penev wrote:
> Allows simplifying get_strings and avoids manual pointer manipulation.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
Reviewed-by: Oleksij Rempel <o.rempel@pengutronix.de>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-08-30 4:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 21:48 [PATCH net-next 0/6] various cleanups Rosen Penev
2024-08-29 21:48 ` [PATCH net-next 1/6] net: ag71xx: add COMPILE_TEST to test compilation Rosen Penev
2024-08-30 15:49 ` Simon Horman
2024-08-30 17:32 ` Rosen Penev
2024-08-30 18:14 ` Simon Horman
2024-08-29 21:48 ` [PATCH net-next 2/6] net: ag71xx: update FIFO bits and descriptions Rosen Penev
2024-08-30 4:54 ` Oleksij Rempel
2024-08-29 21:48 ` [PATCH net-next 3/6] net: ag71xx: use ethtool_puts Rosen Penev
2024-08-30 4:55 ` Oleksij Rempel [this message]
2024-08-29 21:48 ` [PATCH net-next 4/6] net: ag71xx: get reset control using devm api Rosen Penev
2024-08-29 21:48 ` [PATCH net-next 5/6] net: ag71xx: remove always true branch Rosen Penev
2024-08-30 4:56 ` Oleksij Rempel
2024-08-29 21:48 ` [PATCH net-next 6/6] net: ag71xx: disable napi interrupts during probe Rosen Penev
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=ZtFQu777F8bSijGD@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.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.