From: Aswath Govindraju <a-govindraju@ti.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Chandrasekar Ramakrishnan <rcsekar@samsung.com>,
Rob Herring <robh+dt@kernel.org>, <linux-can@vger.kernel.org>,
<netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH v4 0/2] MCAN: Add support for implementing transceiver as a phy
Date: Wed, 28 Jul 2021 10:49:04 +0530 [thread overview]
Message-ID: <7f0316f7-7192-8c68-1800-f4890dac3945@ti.com> (raw)
In-Reply-To: <20210727065416.k2kye47iiuubkpoz@pengutronix.de>
Hi Marc,
On 27/07/21 12:24 pm, Marc Kleine-Budde wrote:
> On 19.07.2021 19:47:33, Aswath Govindraju wrote:
>> I am planning on posting device tree patches to arm64 tree and
>> Nishanth(maintainer of the tree) requested for an immutable tag if the
>> dependent patches are not in master. So, after applying this patch
>> series, can you please provide an immutable tag ?
>
> The patches are included in my pull request with the tag
> linux-can-next-for-5.15-20210725 [1], meanwhile they are in
> net-next/master.
>
> Hope that helps,
> Marc
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/log/?h=linux-can-next-for-5.15-20210725
>
Thanks a lot for providing a tag.
Regards,
Aswath
prev parent reply other threads:[~2021-07-28 5:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 5:25 [PATCH v4 0/2] MCAN: Add support for implementing transceiver as a phy Aswath Govindraju
2021-05-10 5:25 ` [PATCH v4 1/2] dt-bindings: net: can: Document transceiver implementation as phy Aswath Govindraju
2021-05-10 5:25 ` [PATCH v4 2/2] can: m_can: Add support for transceiver " Aswath Govindraju
2021-07-24 17:56 ` Marc Kleine-Budde
2021-06-14 12:32 ` [PATCH v4 0/2] MCAN: Add support for implementing transceiver as a phy Aswath Govindraju
2021-06-16 9:17 ` Marc Kleine-Budde
2021-07-19 14:17 ` Aswath Govindraju
2021-07-27 6:54 ` Marc Kleine-Budde
2021-07-28 5:19 ` Aswath Govindraju [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=7f0316f7-7192-8c68-1800-f4890dac3945@ti.com \
--to=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=rcsekar@samsung.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.