From: Luciano Coelho <luciano.coelho@intel.com>
To: Thomas Backlund <tmb@mageia.org>, gregkh@linuxfoundation.org
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] iwlwifi: fix PCI IDs and configuration mapping for 9000" failed to apply to 4.14-stable tree
Date: Mon, 27 Nov 2017 19:31:05 +0200 [thread overview]
Message-ID: <1511803865.4011.387.camel@intel.com> (raw)
In-Reply-To: <2b9473d6-e145-ffa1-f578-ba8f06955889@mageia.org>
On Mon, 2017-11-27 at 18:39 +0200, Thomas Backlund wrote:
> Den 27.11.2017 kl. 17:21, skrev gregkh@linuxfoundation.org:
> >
> > The patch below does not apply to the 4.14-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
>
>
> In order to get this one to apply nicely I added theese patches to
> Mageia distrib kernel that adds/sorts hw ids to 4.14 branch in the
> below
> order:
Oh, I just sent an updated patch for 4.14 with all the PCI IDs that
were needed for the 9000 series, including the sorting. I'm not sure
what is preferred, if to take a single patch with the needed changes or
to cherry-pick all those other patches that for some reason were not
marked as stable earlier.
Greg?
--
Cheers,
Luca.
next prev parent reply other threads:[~2017-11-27 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 15:21 FAILED: patch "[PATCH] iwlwifi: fix PCI IDs and configuration mapping for 9000" failed to apply to 4.14-stable tree gregkh
2017-11-27 16:39 ` Thomas Backlund
2017-11-27 17:31 ` Luciano Coelho [this message]
2017-11-28 9:12 ` Greg KH
2017-11-28 9:16 ` Luciano Coelho
2017-11-28 9:12 ` Greg KH
2017-11-27 17:28 ` [PATCH] iwlwifi: fix PCI IDs and configuration mapping for 9000 series Luca Coelho
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=1511803865.4011.387.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=tmb@mageia.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.