From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Tero Kristo <kristo@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Lokesh Vutla <lokeshvutla@ti.com>, Faiz Abbas <faiz_abbas@ti.com>
Subject: Re: [PATCH v2 0/6] CAN: Add support for CAN in AM65,J721e and AM64
Date: Wed, 28 Jul 2021 09:26:04 +0200 [thread overview]
Message-ID: <20210728072604.ruev36qwx2x2krlu@pengutronix.de> (raw)
In-Reply-To: <f5abf985-d953-a9cd-f6e6-ee86d3a0f398@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On 28.07.2021 10:49:58, Aswath Govindraju wrote:
> > The following series of patches add support for CAN in SoC's AM65, J721e
> > and AM64.
> >
> > This patch series is dependent on [1] and [2] and I have requested for an
> > immutable tag from the Marc Kleine-Budde(maintainer of net tree).
I'm the maintainer of the "linux-can", not the "net" tree.
> Here is the tag in [0] shared by Marc after applying patches [1] and
> [2], linux-can-next-for-5.15-20210725,
>
> [0] -
> https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/log/?h=linux-can-next-for-5.15-20210725
That tag has been merged by David Miller into the net-next tree.
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d20e5880fe9df149a9159673d9fec57aab43ac61
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-28 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 10:10 [PATCH v2 0/6] CAN: Add support for CAN in AM65,J721e and AM64 Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 1/6] arm64: dts: ti: k3-am65-mcu: Add Support for MCAN Aswath Govindraju
2021-08-02 12:59 ` Marc Kleine-Budde
2021-07-26 10:10 ` [PATCH v2 2/6] arm64: dts: ti: am654-base-board: Disable mcan nodes Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 3/6] arm64: dts: ti: k3-j721e: Add support for MCAN nodes Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 4/6] arm64: dts: ti: k3-j721e-common-proc-board: Add support for mcu_mcan nodes Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 5/6] arm64: dts: ti: k3-am64-main: Add support for MCAN Aswath Govindraju
2021-07-26 10:10 ` [PATCH v2 6/6] arm64: dts: ti: k3-am642-evm/sk: Add support for main domain mcan nodes in EVM and disable them on SK Aswath Govindraju
2021-07-28 5:19 ` [PATCH v2 0/6] CAN: Add support for CAN in AM65,J721e and AM64 Aswath Govindraju
2021-07-28 7:26 ` Marc Kleine-Budde [this message]
2021-08-02 12:45 ` Nishanth Menon
2021-08-05 12:32 ` Aswath Govindraju
2021-08-05 12:40 ` Jan Kiszka
2021-08-05 12:44 ` Aswath Govindraju
2021-08-05 12:49 ` Jan Kiszka
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=20210728072604.ruev36qwx2x2krlu@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh+dt@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).