From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "marek.vasut+renesas@gmail.com" <marek.vasut+renesas@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v4 1/2] Revert "PCI: rcar: Fix missing MACCTLR register setting in rcar_pcie_hw_init()"
Date: Tue, 12 Nov 2019 01:26:16 +0000 [thread overview]
Message-ID: <TYAPR01MB4544C4D4103EC2C9ACFB672ED8770@TYAPR01MB4544.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20191111143853.GA9653@e121166-lin.cambridge.arm.com>
Hi Lorenzo,
> From: Lorenzo Pieralisi, Sent: Monday, November 11, 2019 11:39 PM
>
> On Tue, Nov 05, 2019 at 07:51:28PM +0900, Yoshihiro Shimoda wrote:
> > This reverts commit 175cc093888ee74a17c4dd5f99ba9a6bc86de5be.
> >
> > The commit description/code don't follow the manual accurately,
> > it's difficult to understand. So, this patch reverts the commit.
> >
> > Fixes: 175cc093888e ("PCI: rcar: Fix missing MACCTLR register setting in rcar_pcie_hw_init()"
>
> This patch is not in the mainline, I will just drop it.
I got it.
> > Cc: <stable@vger.kernel.org>
>
> This is valid for any fix: there is no reason to send to stable a fix
> for a patch that is not in the mainline yet.
I understood it. So, I'll drop both tags on v5 patches.
Best regards,
Yoshihiro Shimoda
next prev parent reply other threads:[~2019-11-12 1:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 10:51 [PATCH v4 0/2] PCI: rcar: Fix missing MACCTLR register setting (take2) Yoshihiro Shimoda
2019-11-05 10:51 ` [PATCH v4 1/2] Revert "PCI: rcar: Fix missing MACCTLR register setting in rcar_pcie_hw_init()" Yoshihiro Shimoda
2019-11-11 14:38 ` Lorenzo Pieralisi
2019-11-12 1:26 ` Yoshihiro Shimoda [this message]
2019-11-05 10:51 ` [PATCH v4 2/2] PCI: rcar: Fix missing MACCTLR register setting in initialize sequence Yoshihiro Shimoda
2019-11-11 14:42 ` Lorenzo Pieralisi
2019-11-12 1:48 ` Yoshihiro Shimoda
2019-11-12 10:27 ` Lorenzo Pieralisi
2019-11-12 10:46 ` Geert Uytterhoeven
2019-11-12 11:25 ` Lorenzo Pieralisi
2019-11-13 1:34 ` Yoshihiro Shimoda
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=TYAPR01MB4544C4D4103EC2C9ACFB672ED8770@TYAPR01MB4544.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marek.vasut+renesas@gmail.com \
--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 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).