From: Fabio Estevam <festevam@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Baruch Siach <baruch@tkos.co.il>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: imx: Fix the AR803X phy-mode
Date: Tue, 2 Apr 2019 13:26:51 -0300 [thread overview]
Message-ID: <CAOMZO5CHT511ipMud8f8dmMXu08spqcYsq9A9nOuMNsNs=DYVg@mail.gmail.com> (raw)
In-Reply-To: <20190402154825.A0DBB207E0@mail.kernel.org>
On Tue, Apr 2, 2019 at 12:48 PM Sasha Levin <sashal@kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: 4.9+
>
> The bot has tested the following trees: v5.0.5, v4.19.32, v4.14.109, v4.9.166.
> How should we proceed with this patch?
I can manually generate versions for 4.9, 4.14 and 4.19 stable trees
when this one hit mainline.
WARNING: multiple messages have this Message-ID (diff)
From: Fabio Estevam <festevam@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Baruch Siach <baruch@tkos.co.il>, Shawn Guo <shawnguo@kernel.org>,
stable <stable@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: imx: Fix the AR803X phy-mode
Date: Tue, 2 Apr 2019 13:26:51 -0300 [thread overview]
Message-ID: <CAOMZO5CHT511ipMud8f8dmMXu08spqcYsq9A9nOuMNsNs=DYVg@mail.gmail.com> (raw)
In-Reply-To: <20190402154825.A0DBB207E0@mail.kernel.org>
On Tue, Apr 2, 2019 at 12:48 PM Sasha Levin <sashal@kernel.org> wrote:
>
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: 4.9+
>
> The bot has tested the following trees: v5.0.5, v4.19.32, v4.14.109, v4.9.166.
> How should we proceed with this patch?
I can manually generate versions for 4.9, 4.14 and 4.19 stable trees
when this one hit mainline.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-02 16:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 12:47 [PATCH] ARM: dts: imx: Fix the AR803X phy-mode Fabio Estevam
2019-04-01 12:47 ` Fabio Estevam
2019-04-01 17:55 ` Michael Grzeschik
2019-04-01 17:55 ` Michael Grzeschik
2019-04-01 19:47 ` Fabio Estevam
2019-04-01 19:47 ` Fabio Estevam
2019-04-02 5:52 ` Michael Grzeschik
2019-04-02 5:52 ` Michael Grzeschik
2019-04-02 11:06 ` Fabio Estevam
2019-04-02 11:06 ` Fabio Estevam
2019-04-02 13:21 ` Andrew Lunn
2019-04-02 13:21 ` Andrew Lunn
2019-04-03 6:40 ` Michael Grzeschik
2019-04-03 6:40 ` Michael Grzeschik
2019-04-08 10:44 ` Michael Grzeschik
2019-04-08 10:44 ` Michael Grzeschik
2019-04-02 15:48 ` Sasha Levin
2019-04-02 16:26 ` Fabio Estevam [this message]
2019-04-02 16:26 ` Fabio Estevam
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='CAOMZO5CHT511ipMud8f8dmMXu08spqcYsq9A9nOuMNsNs=DYVg@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sashal@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stable@vger.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 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.