From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: ethernet: renesas: infrastructure preparations for upcoming driver
Date: Mon, 23 Oct 2023 10:51:13 +0200 [thread overview]
Message-ID: <ZTY0AXS2QtkIkLX7@oden.dyn.berto.se> (raw)
In-Reply-To: <20231022205316.3209-1-wsa+renesas@sang-engineering.com>
Hi Wolfram,
Nice work, for the whole series.
Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
On 2023-10-22 22:53:14 +0200, Wolfram Sang wrote:
> Before we upstream a new driver, Niklas and I thought that a few
> cleanups for Kconfig/Makefile will help readability and maintainability.
> Here they are, looking forward to comments.
>
>
> Wolfram Sang (2):
> net: ethernet: renesas: group entries in Makefile
> net: ethernet: renesas: drop SoC names in Kconfig
>
> drivers/net/ethernet/renesas/Kconfig | 9 +--------
> drivers/net/ethernet/renesas/Makefile | 4 +---
> 2 files changed, 2 insertions(+), 11 deletions(-)
>
> --
> 2.35.1
>
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2023-10-23 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 20:53 [PATCH net-next 0/2] net: ethernet: renesas: infrastructure preparations for upcoming driver Wolfram Sang
2023-10-22 20:53 ` [PATCH net-next 1/2] net: ethernet: renesas: group entries in Makefile Wolfram Sang
2023-10-23 8:45 ` Sergey Shtylyov
2023-10-23 9:12 ` Wolfram Sang
2023-10-22 20:53 ` [PATCH net-next 2/2] net: ethernet: renesas: drop SoC names in Kconfig Wolfram Sang
2023-10-23 8:48 ` Sergey Shtylyov
2023-10-24 10:53 ` Paolo Abeni
2023-10-24 13:04 ` Geert Uytterhoeven
2023-10-23 8:51 ` Niklas Söderlund [this message]
2023-10-24 23:30 ` [PATCH net-next 0/2] net: ethernet: renesas: infrastructure preparations for upcoming driver patchwork-bot+netdevbpf
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=ZTY0AXS2QtkIkLX7@oden.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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 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).