From: Luciano Coelho <luciano.coelho@intel.com>
To: Hauke Mehrtens <hauke@hauke-m.de>, backports@vger.kernel.org
Subject: Re: [PATCH 00/10] backport: updates for v4.16
Date: Mon, 19 Feb 2018 10:08:02 +0200 [thread overview]
Message-ID: <1519027682.7832.80.camel@intel.com> (raw)
In-Reply-To: <c212f7c3-f5d6-543f-26ba-ef1c55221261@hauke-m.de>
On Sun, 2018-02-18 at 17:11 +0100, Hauke Mehrtens wrote:
> On 02/18/2018 02:24 PM, Luca Coelho wrote:
> > From: Luca Coelho <luciano.coelho@intel.com>
> >
> > Hi,
> >
> > Here's a bunch of patches that we had pending in our internal
> > backports tree. With this series at least iwlwifi can be fully
> > backported from v4.16 kernels.
>
> Thanks for the patches they are looking good to me.
>
> With which kernels have you tested these patches + iwlwifi?
I have compile-tested these patches with our internal iwlwifi tree
(which is essentially a backport from wireless-drivers-next and
contains iwlwifi, mac80211, cfg80211 and other small things) on 4.4,
4.14 and 4.15 (at least). And we also have automated builds that
compile-test on these kernels: 3.10, 3.16, 3.18, 4.1, 4.4, 4.6 and 4.9.
We also have an old build machine that uses 3.8. I have an extra patch
to hack the compilation on it, but I didn't send it upstream because we
agreed to support backports only on 3.10+. And my patch just comments
out some stuff to make it compile...
--
Cheers,
Luca.
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-02-19 8:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 13:24 [PATCH 00/10] backport: updates for v4.16 Luca Coelho
2018-02-18 13:24 ` [PATCH 01/10] compat: only define thermal backports if CONFIG_THERMAL is enabled Luca Coelho
2018-02-18 13:24 ` [PATCH 02/10] backport: add pcie_find_root_port() Luca Coelho
2018-02-18 13:24 ` [PATCH 03/10] backport: include lib/bucket_locks.c Luca Coelho
2018-02-18 13:24 ` [PATCH 04/10] backport: update genl_dump_check_consistent() backport Luca Coelho
2018-02-18 13:24 ` [PATCH 05/10] backport: remove pkcs7_verify.c patch hunk Luca Coelho
2018-02-18 13:24 ` [PATCH 06/10] backport: add new build_bug.h file Luca Coelho
2018-02-18 13:24 ` [PATCH 07/10] backports: fix typo "TIMKEEPING" and fix gfp.h Luca Coelho
2018-02-18 13:24 ` [PATCH 08/10] backport: remove stddef.h inclusions Luca Coelho
2018-02-18 13:24 ` [PATCH 09/10] backport: increase max stack frame size compiler check to 1280 Luca Coelho
2018-02-18 13:24 ` [PATCH 10/10] backport: implement alloc_percpu_gfp() for < 3.18 Luca Coelho
2018-02-18 16:10 ` Hauke Mehrtens
2018-02-18 17:58 ` Luciano Coelho
2018-02-28 18:32 ` Hauke Mehrtens
2018-02-28 18:48 ` Luca Coelho
2018-02-18 16:11 ` [PATCH 00/10] backport: updates for v4.16 Hauke Mehrtens
2018-02-19 8:08 ` Luciano Coelho [this message]
2018-02-23 11:35 ` Johannes Berg
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=1519027682.7832.80.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
/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.