From: Jakub Kicinski <kuba@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
Herve Codina <herve.codina@bootlin.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH 0/5] Add support for framer infrastructure and PEF2256 framer
Date: Tue, 28 Nov 2023 17:31:10 -0800 [thread overview]
Message-ID: <20231128173110.0ccb8f53@kernel.org> (raw)
In-Reply-To: <CACRpkdYmN4318b1wXwUOeFjPN0S2w8M9FpXHOs3LtFa+XoTxVw@mail.gmail.com>
On Tue, 28 Nov 2023 15:51:01 +0100 Linus Walleij wrote:
> > > I thought this thing would be merged primarily into the networking
> > > tree, and I don't know if they do signed tags, I usually create an
> > > immutable branch but that should work just as fine I guess.
> >
> > Right, I'd expect a signed tag on the immutable branch - it's generally
> > helpful to avoid confusion about the branch actually being immutable.
>
> Makes sense, best to create that in the netdev tree if possible
> I guess.
I think you offered creating the branch / tag in an earlier reply,
that's less work for me so yes please! :)
FWIW I usually put the branches / tags in my personal k.org tree.
I don't wanna pollute the trees for the $many people who fetch
netdev with random tags.
next prev parent reply other threads:[~2023-11-29 1:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 13:25 [PATCH 0/5] Add support for framer infrastructure and PEF2256 framer Herve Codina
2023-11-28 13:25 ` [PATCH 1/5] net: wan: Add framer framework support Herve Codina
2023-11-28 13:25 ` [PATCH 2/5] dt-bindings: net: Add the Lantiq PEF2256 E1/T1/J1 framer Herve Codina
2023-11-28 13:25 ` [PATCH 3/5] net: wan: framer: Add support for the Lantiq PEF2256 framer Herve Codina
2023-11-28 13:25 ` [PATCH 4/5] pinctrl: Add support for the Lantic PEF2256 pinmux Herve Codina
2023-11-28 13:25 ` [PATCH 5/5] MAINTAINERS: Add the Lantiq PEF2256 driver entry Herve Codina
2023-11-28 14:03 ` [PATCH 0/5] Add support for framer infrastructure and PEF2256 framer Mark Brown
2023-11-28 14:26 ` Linus Walleij
2023-11-28 14:41 ` Mark Brown
2023-11-28 14:51 ` Linus Walleij
2023-11-29 1:31 ` Jakub Kicinski [this message]
2023-11-29 14:00 ` Linus Walleij
2023-12-12 9:59 ` Herve Codina
2023-12-12 22:15 ` Linus Walleij
2023-12-13 0:00 ` Jakub Kicinski
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=20231128173110.0ccb8f53@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=herve.codina@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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).