linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Colin Foster <colin.foster@in-advantage.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-gpio@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Lars Povlsen <lars.povlsen@microchip.com>,
	Steen Hegelund <Steen.Hegelund@microchip.com>,
	UNGLinuxDriver@microchip.com, Wolfram Sang <wsa@kernel.org>,
	Terry Bowman <terry.bowman@amd.com>,
	katie.morris@in-advantage.com
Subject: Re: [PATCH v13 net-next 0/9] add support for VSC7512 control over SPI
Date: Mon, 11 Jul 2022 11:21:16 -0700	[thread overview]
Message-ID: <20220711112116.2f931390@kernel.org> (raw)
In-Reply-To: <YsvWh8YJGeJNbQFB@google.com>

On Mon, 11 Jul 2022 08:51:35 +0100 Lee Jones wrote:
> > Can this go into net-next if there are no more complains over the
> > weekend? Anyone still planning to review?  
> 
> As the subsystem with the fewest changes, I'm not sure why it would.

Yeah, just going by the tag in the subject. I have no preference,
looks like it applies cleanly to Linus'.

> I'd planed to route this in via MFD and send out a pull-request for
> other sub-system maintainers to pull from.
> 
> If you would like to co-ordinate it instead, you'd be welcome to.
> However, I (and probably Linus) would need a succinct immutable branch
> to pull from.

Oh, that'd be perfect, sorry, I didn't realize there was already a plan.
If you're willing to carry on as intended, please do.

Colin if there is another version please make a note of the above
merging plan in the cover letter and drop the net-next tag. 
Just in  case my goldfish brain forgets.

  reply	other threads:[~2022-07-11 18:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 20:47 [PATCH v13 net-next 0/9] add support for VSC7512 control over SPI Colin Foster
2022-07-05 20:47 ` [PATCH v13 net-next 1/9] mfd: ocelot: add helper to get regmap from a resource Colin Foster
2022-07-09 18:56   ` Vladimir Oltean
2022-07-05 20:47 ` [PATCH v13 net-next 2/9] net: mdio: mscc-miim: add ability to be used in a non-mmio configuration Colin Foster
2022-07-09 18:57   ` Vladimir Oltean
2022-07-11 18:22   ` Jakub Kicinski
2022-07-05 20:47 ` [PATCH v13 net-next 3/9] pinctrl: ocelot: allow pinctrl-ocelot to be loaded as a module Colin Foster
2022-07-05 20:47 ` [PATCH v13 net-next 4/9] pinctrl: ocelot: add ability to be used in a non-mmio configuration Colin Foster
2022-07-09 18:59   ` Vladimir Oltean
2022-07-11  8:20   ` Linus Walleij
2022-07-05 20:47 ` [PATCH v13 net-next 5/9] pinctrl: microchip-sgpio: allow sgpio driver to be used as a module Colin Foster
2022-07-05 20:47 ` [PATCH v13 net-next 6/9] pinctrl: microchip-sgpio: add ability to be used in a non-mmio configuration Colin Foster
2022-07-09 18:58   ` Vladimir Oltean
2022-07-11  8:19   ` Linus Walleij
2022-07-05 20:47 ` [PATCH v13 net-next 7/9] resource: add define macro for register address resources Colin Foster
2022-07-09 19:00   ` Vladimir Oltean
2022-07-05 20:47 ` [PATCH v13 net-next 8/9] dt-bindings: mfd: ocelot: add bindings for VSC7512 Colin Foster
2022-07-11 13:25   ` Vladimir Oltean
2022-07-05 20:47 ` [PATCH v13 net-next 9/9] mfd: ocelot: add support for the vsc7512 chip via spi Colin Foster
2022-07-11 13:27   ` Vladimir Oltean
2022-07-18 14:18   ` Lee Jones
2022-07-18 16:24     ` Colin Foster
2022-07-19 17:49     ` Colin Foster
2022-07-20  8:19       ` Lee Jones
2022-07-09  3:09 ` [PATCH v13 net-next 0/9] add support for VSC7512 control over SPI Jakub Kicinski
2022-07-11  7:51   ` Lee Jones
2022-07-11 18:21     ` Jakub Kicinski [this message]
2022-07-12  2:10       ` Colin Foster
2022-07-12 22:08         ` Vladimir Oltean
2022-07-15 16:57           ` Colin Foster
2022-07-18  8:14             ` Lee Jones

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=20220711112116.2f931390@kernel.org \
    --to=kuba@kernel.org \
    --cc=Steen.Hegelund@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=andy.shevchenko@gmail.com \
    --cc=colin.foster@in-advantage.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=katie.morris@in-advantage.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars.povlsen@microchip.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.org \
    --cc=terry.bowman@amd.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=wsa@kernel.org \
    /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).