From: Markus Elfring <Markus.Elfring@web.de>
To: Jakub Kicinski <jakub.kicinski@netronome.com>, netdev@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Pawel Dembicki <paweldembicki@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [0/2] net: dsa: vsc73xx: Adjustments for vsc73xx_platform_probe()
Date: Sat, 21 Sep 2019 09:12:44 +0200 [thread overview]
Message-ID: <a5e3f8e6-bdb9-c5fb-2435-81a545cad121@web.de> (raw)
In-Reply-To: <20190920151230.0d290654@cakuba.netronome.com>
> Indeed, looks like we have a mix of clean ups of varying clarity here.
> I will just drop all, including the devm_platform_ioremap_resource()
> conversion patches from patchwork for now.
I would prefer an other patch management in this case.
> Markus, please repost them all once net-next opens.
> Sorry for inconvenience.
I would find it nicer if presented change possibilities can be
automatically reconsidered on demand after each closed period.
https://patchwork.ozlabs.org/project/netdev/list/?submitter=76334&state=*
https://patchwork.ozlabs.org/project/netdev/list/?submitter=65077&state=*&archive=both
Regards,
Markus
prev parent reply other threads:[~2019-09-21 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 14:25 [PATCH 0/2] net: dsa: vsc73xx: Adjustments for vsc73xx_platform_probe() Markus Elfring
2019-09-20 14:28 ` [PATCH 1/2] net: dsa: vsc73xx: Use devm_platform_ioremap_resource() in vsc73xx_platform_probe() Markus Elfring
2019-09-20 15:08 ` Andrew Lunn
2019-09-20 14:30 ` [PATCH 2/2] net: dsa: vsc73xx: Return an error code as a constant " Markus Elfring
2019-09-20 15:08 ` Andrew Lunn
2019-09-20 15:09 ` [PATCH 0/2] net: dsa: vsc73xx: Adjustments for vsc73xx_platform_probe() Andrew Lunn
2019-09-20 15:30 ` [0/2] " Markus Elfring
2019-09-20 16:36 ` Florian Fainelli
2019-09-20 22:12 ` Jakub Kicinski
2019-09-21 7:12 ` Markus Elfring [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=a5e3f8e6-bdb9-c5fb-2435-81a545cad121@web.de \
--to=markus.elfring@web.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paweldembicki@gmail.com \
--cc=vivien.didelot@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 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).