From: Sasha Levin <sasha.levin@oracle.com>
To: Simon Horman <horms@verge.net.au>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [added to the 4.1 stable tree] usb: host: xhci-rcar: Use ARCH_RENESAS
Date: Fri, 3 Jun 2016 21:14:17 -0400 [thread overview]
Message-ID: <57522B69.3070105@oracle.com> (raw)
In-Reply-To: <20160604004717.GB469@verge.net.au>
On 06/03/2016 08:47 PM, Simon Horman wrote:
> Hi,
>
> I do not believe this patch is suitable for v4.1 stable.
>
> ARCH_RENESAS is not otherwise present there and thus the driver in question
> will stop being compiled where it was previously compiled.
>
> Moreover, the transition to ARCH_RENESAS is (so far) being handled in such
> a way that there have not been any regressions that would necessitate a
> backport to -stable.
Hey Simon,
I've picked this commit because of what I saw in f879fc32a
("usb: host: xhci-rcar: Avoid long wait in xhci_reset()").
>From my understanding of that change, we added a dependency on ARCH_RENESAS
for USB_XHCI_PLATFORM, but since USB_XHCI_RCAR depended on ARCH_SHMOBILE that
would cause silly errors for kconfig and would probably confuse users.
Rather than changing it to a ARCH_SHMOBILE dependency, I've preferred
to pull in f879fc32a to keep the stable tree more aligned with upstream
and possibly prevent any future backporting errors for new commits that
add ARCH_RENESAS dependencies.
If you don't agree with that approach I can change that to a ARCH_SHMOBILE
dependency and remove this commit, or take any other approach you think
is better?
Thanks,
Sasha
next prev parent reply other threads:[~2016-06-04 1:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464989831-16666-1-git-send-email-sasha.levin@oracle.com>
[not found] ` <1464989831-16666-66-git-send-email-sasha.levin@oracle.com>
2016-06-04 0:47 ` [added to the 4.1 stable tree] usb: host: xhci-rcar: Use ARCH_RENESAS Simon Horman
2016-06-04 1:14 ` Sasha Levin [this message]
2016-06-06 0:39 ` Simon Horman
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=57522B69.3070105@oracle.com \
--to=sasha.levin@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=stable-commits@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox