From: Fabio Estevam <festevam@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Koen Vandeputte <koen.vandeputte@ncentric.com>,
linux-pci@vger.kernel.org,
Binghui Wang <wangbinghui@hisilicon.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Jianguo Sun <sunjianguo1@huawei.com>,
Jingoo Han <jingoohan1@gmail.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Lucas Stach <l.stach@pengutronix.de>,
Minghuan Lian <minghuan.Lian@freescale.com>,
Mingkai Hu <mingkai.hu@freescale.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Pratyush Anand <pratyush.anand@gmail.com>,
Richard Zhu <hongxing.zhu@nxp.com>,
Roy Zang <tie-fei.zang@freescale.com>,
Shawn Guo <shawn.guo@linaro.org>,
Stanimir Varbanov <svarbanov@mm-sol.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Xiaowei Song <songxiaowei@hisilicon.com>,
Zhou Wang <wangzhou1@hisilicon.com>
Subject: Re: [PATCH v2] PCI: dwc: fix enumeration end when reaching root subordinate
Date: Mon, 5 Feb 2018 20:12:48 -0200 [thread overview]
Message-ID: <CAOMZO5ArPt2MMVp5g0FD8v=HtMOcja8XUH9BkSZ-n-wMqrLo3A@mail.gmail.com> (raw)
In-Reply-To: <20180205200648.GM27654@lahna.fi.intel.com>
Hi Mika
On Mon, Feb 5, 2018 at 6:06 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> BTW, this should have a stable tag so that it gets backported to stable
> kernels. I guess whoever is applying the patch can add it so no need for
> another revision.
I agree it needs to be backported to stable as I adapted this patch to
4.9 and it fixed the issue there.
However the Fixes lines mentions commit a20c7f36bd3d, which only
appears in 4.15, so that is confusing for backporting to older
kernels.
next prev parent reply other threads:[~2018-02-05 22:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 9:36 [PATCH v2] PCI: dwc: fix enumeration end when reaching root subordinate Koen Vandeputte
2018-01-15 11:50 ` Mason
2018-01-15 19:47 ` Fabio Estevam
2018-01-15 19:52 ` Mika Westerberg
2018-02-05 19:14 ` Lorenzo Pieralisi
2018-02-05 20:06 ` Mika Westerberg
2018-02-05 22:12 ` Fabio Estevam [this message]
2018-02-14 15:41 ` Fabio Estevam
2018-02-14 15:49 ` Lucas Stach
2018-02-06 10:44 ` [v2] " Sebastian Reichel
2018-02-20 15:39 ` [PATCH v2] " Lorenzo Pieralisi
2018-03-02 22:57 ` Fabio Estevam
2018-03-05 9:49 ` Lorenzo Pieralisi
2018-03-05 11:55 ` Fabio Estevam
2018-03-05 12:24 ` Lorenzo Pieralisi
2018-03-05 13:08 ` Kishon Vijay Abraham I
2018-03-06 8:16 ` Shawn Guo
2018-03-06 10:13 ` Niklas Cassel
2018-03-07 17:13 ` Lorenzo Pieralisi
2018-03-07 17:23 ` Fabio Estevam
2018-03-12 13:31 ` 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='CAOMZO5ArPt2MMVp5g0FD8v=HtMOcja8XUH9BkSZ-n-wMqrLo3A@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=bhelgaas@google.com \
--cc=hongxing.zhu@nxp.com \
--cc=jesper.nilsson@axis.com \
--cc=jingoohan1@gmail.com \
--cc=kishon@ti.com \
--cc=koen.vandeputte@ncentric.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=m-karicheri2@ti.com \
--cc=mika.westerberg@linux.intel.com \
--cc=minghuan.Lian@freescale.com \
--cc=mingkai.hu@freescale.com \
--cc=pratyush.anand@gmail.com \
--cc=shawn.guo@linaro.org \
--cc=songxiaowei@hisilicon.com \
--cc=sunjianguo1@huawei.com \
--cc=svarbanov@mm-sol.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tie-fei.zang@freescale.com \
--cc=wangbinghui@hisilicon.com \
--cc=wangzhou1@hisilicon.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.