From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Simon Horman <simon.horman@corigine.com>
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
kernel@pengutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/4] net: set 'mac_managed_pm' at probe time
Date: Wed, 15 Mar 2023 08:26:33 +0100 [thread overview]
Message-ID: <ZBFzKatnFs7MraVn@ninjato> (raw)
In-Reply-To: <ZBCjj6btYod38O7g@corigine.com>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
Hi Simon!
> an initial comment is, and I know this is a bit of a pain,
> that 'net' and 'net-next' patches need to be split into separate serries.
Thanks for the heads up. I will refactor the series. First a part which
shall go into "net" and I will make the second part RFC with more
explanations how to reproduce the issue.
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-03-15 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 13:14 [PATCH net 0/4] net: set 'mac_managed_pm' at probe time Wolfram Sang
2023-03-14 13:14 ` [PATCH net 1/4] ravb: avoid PHY being resumed when interface is not up Wolfram Sang
2023-03-14 13:14 ` [PATCH net 2/4] sh_eth: " Wolfram Sang
2023-03-14 13:14 ` [PATCH net-next 3/4] fec: add FIXME to move 'mac_managed_pm' to probe Wolfram Sang
2023-03-15 5:48 ` Wei Fang
2023-03-15 7:27 ` Wolfram Sang
2023-03-16 8:02 ` Wolfram Sang
2023-03-16 9:10 ` Wei Fang
2023-03-16 13:53 ` Wolfram Sang
2023-03-14 13:14 ` [PATCH net-next 4/4] smsc911x: " Wolfram Sang
2023-03-15 8:50 ` Geert Uytterhoeven
2023-03-15 8:52 ` Wolfram Sang
2023-03-14 15:56 ` [PATCH net 0/4] net: set 'mac_managed_pm' at probe time Michal Kubiak
2023-03-14 16:40 ` Simon Horman
2023-03-15 7:26 ` Wolfram Sang [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=ZBFzKatnFs7MraVn@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@corigine.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).