From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Realtek linux nic maintainers <nic_swsd@realtek.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/3] r8169: small improvements
Date: Wed, 6 Jan 2021 19:10:37 +0100 [thread overview]
Message-ID: <8b5980de-2c6b-d2ca-e5ba-f93a839099c7@gmail.com> (raw)
In-Reply-To: <f89bf2f3-5324-b635-4253-8a8be316c15b@gmail.com>
On 06.01.2021 14:26, Heiner Kallweit wrote:
> This series includes a number of smaller improvements.
>
> Heiner Kallweit (3):
> r8169: replace BUG_ON with WARN in _rtl_eri_write
> r8169: improve rtl_ocp_reg_failure
> r8169: don't wakeup-enable device on shutdown if WOL is disabled
>
> drivers/net/ethernet/realtek/r8169_main.c | 21 ++++++++-------------
> 1 file changed, 8 insertions(+), 13 deletions(-)
>
Just saw that this series is marked "doesn't apply on net-next" in
patchwork. I checked and indeed there's a dependency on prior,
not yet applied series
[PATCH net-next 0/2] r8169: improve RTL8168g PHY suspend quirk
Shall I resend once the first series is applied?
next prev parent reply other threads:[~2021-01-06 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 13:26 [PATCH net-next 0/3] r8169: small improvements Heiner Kallweit
2021-01-06 13:28 ` [PATCH net-next 1/3] r8169: replace BUG_ON with WARN in _rtl_eri_write Heiner Kallweit
2021-01-06 22:18 ` Alexander Duyck
2021-01-06 23:02 ` Heiner Kallweit
2021-01-06 13:28 ` [PATCH net-next 2/3] r8169: improve rtl_ocp_reg_failure Heiner Kallweit
2021-01-06 13:29 ` [PATCH net-next 3/3] r8169: don't wakeup-enable device on shutdown if WOL is disabled Heiner Kallweit
2021-01-06 18:10 ` Heiner Kallweit [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-25 18:42 [PATCH net-next 0/3] r8169: small improvements Heiner Kallweit
2019-05-27 5:21 ` David Miller
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=8b5980de-2c6b-d2ca-e5ba-f93a839099c7@gmail.com \
--to=hkallweit1@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.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.