From: Sinan Kaya <okaya@codeaurora.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, sulrich@codeaurora.org,
timur@codeaurora.org, linux-arm-msm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
open list <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: quirk HT1100 & HT2000 and one HT2100 Root Ports for Extended Tags
Date: Wed, 11 Apr 2018 10:13:11 -0400 [thread overview]
Message-ID: <1290e3d3-e7f0-a4f5-925d-2b7c2cb42b93@codeaurora.org> (raw)
In-Reply-To: <20180411140849.GA12557@kroah.com>
On 4/11/2018 10:08 AM, Greg Kroah-Hartman wrote:
>>> So I added these stable tags:
>>>
>>> CC: stable@vger.kernel.org # v4.11: 62ce94a7a5a5 PCI: Mark Broadcom HT2100 Root Port Extended Tags as broken
>>> CC: stable@vger.kernel.org # v4.11
>>>
>>> I'm not sure I'm using the stable request correctly, but my intent is:
Asking if we placed the tags correctly. Sounds like we did.
>>>
>>> - 62ce94a7a5a5 appeared in v4.14, so cherry-pick 62ce94a7a5a5 to
>>> v4.11 through v4.13
>>> - cherry-pick *this* patch on top of 62ce94a7a5a5 to v4.11 and later
> Bjorn is correct here, why are you dragging me into this?
Thanks
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-04-11 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 22:50 [PATCH] PCI: quirk HT1100 & HT2000 and one HT2100 Root Ports for Extended Tags Sinan Kaya
2018-04-10 19:41 ` Bjorn Helgaas
2018-04-10 19:50 ` Bjorn Helgaas
2018-04-10 20:18 ` Sinan Kaya
2018-04-11 13:51 ` Bjorn Helgaas
2018-04-11 14:02 ` Sinan Kaya
2018-04-11 14:08 ` Greg Kroah-Hartman
2018-04-11 14:13 ` Sinan Kaya [this message]
2018-04-11 14:19 ` Greg Kroah-Hartman
2018-04-11 16:23 ` Sinan Kaya
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=1290e3d3-e7f0-a4f5-925d-2b7c2cb42b93@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sulrich@codeaurora.org \
--cc=timur@codeaurora.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