All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: gregkh@linuxfoundation.org, mika.westerberg@linux.intel.com,
	rafael.j.wysocki@intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ACPI / scan: Fix enumeration for special SPI and I2C devices" failed to apply to 4.11-stable tree
Date: Mon, 26 Jun 2017 10:38:16 +0300	[thread overview]
Message-ID: <9088d5f6-7d06-ac80-defa-1a0f3ac00a64@linux.intel.com> (raw)
In-Reply-To: <1498457053234198@kroah.com>

Hi

On 06/26/2017 09:04 AM, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 4.11-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> thanks,
>
> greg k-h
>
> ------------------ original commit in Linus's tree ------------------
>
> From e4330d8bf669139a983255d1801733b64c2ae841 Mon Sep 17 00:00:00 2001
> From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> Date: Mon, 19 Jun 2017 15:53:01 +0300
> Subject: [PATCH] ACPI / scan: Fix enumeration for special SPI and I2C devices
>
Rafael: this was meant to queue to stable either together with commit 
f5beabfe6179 ("ACPI / scan: Apply default enumeration to devices with 
ACPI drivers") or have another version.

Although I don't know does f5beabfe6179 fix any regression I think best 
would be to queue them together as end result will be the same if I cook 
another version for stable.

-- 
Jarkko

  reply	other threads:[~2017-06-26  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26  6:04 FAILED: patch "[PATCH] ACPI / scan: Fix enumeration for special SPI and I2C devices" failed to apply to 4.11-stable tree gregkh
2017-06-26  7:38 ` Jarkko Nikula [this message]
2017-06-26 12:20   ` Greg KH

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=9088d5f6-7d06-ac80-defa-1a0f3ac00a64@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.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 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.