All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian W MORRISON <ianwmorrison@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: rodrigo.vivi@intel.com, anusha.srivatsa@intel.com,
	michal.wajdeczko@intel.com, Greg KH <gregkh@linuxfoundation.org>,
	airlied@linux.ie, joonas.lahtinen@linux.intel.com,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake
Date: Wed, 11 Apr 2018 20:41:56 +1000	[thread overview]
Message-ID: <CAFXWsS_SvkLvJcibx9LoUw+onN-AAzSLMrRgx3U3hsbMVyty2g@mail.gmail.com> (raw)
In-Reply-To: <871sfmhz88.fsf@intel.com>

<snip>

>
> NAK on indiscriminate Cc: stable. There are zero guarantees that older
> kernels will work with whatever firmware you throw at them.
>

I included 'Cc: stable' so the patch would get added to the v4.16 and
v4.15 kernels
which I have tested with the patch. I found that earlier kernels
didn't support the
'linux-firmware' package required to get wifi working on Intel's new
Gemini Lake NUC.

>
> PS. How is this a "RESEND"? I haven't seen this before.
>

It is a 'RESEND' for that very reason. I initially sent the patch to
the same people as
a similar patch (https://patchwork.kernel.org/patch/10143637/) however
after realising
this omitted required addresses I added them and resent the patch.

Best regards,
Ian

WARNING: multiple messages have this Message-ID (diff)
From: Ian W MORRISON <ianwmorrison@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: anusha.srivatsa@intel.com, airlied@linux.ie,
	Greg KH <gregkh@linuxfoundation.org>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
	rodrigo.vivi@intel.com, michal.wajdeczko@intel.com
Subject: Re: [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake
Date: Wed, 11 Apr 2018 20:41:56 +1000	[thread overview]
Message-ID: <CAFXWsS_SvkLvJcibx9LoUw+onN-AAzSLMrRgx3U3hsbMVyty2g@mail.gmail.com> (raw)
In-Reply-To: <871sfmhz88.fsf@intel.com>

<snip>

>
> NAK on indiscriminate Cc: stable. There are zero guarantees that older
> kernels will work with whatever firmware you throw at them.
>

I included 'Cc: stable' so the patch would get added to the v4.16 and
v4.15 kernels
which I have tested with the patch. I found that earlier kernels
didn't support the
'linux-firmware' package required to get wifi working on Intel's new
Gemini Lake NUC.

>
> PS. How is this a "RESEND"? I haven't seen this before.
>

It is a 'RESEND' for that very reason. I initially sent the patch to
the same people as
a similar patch (https://patchwork.kernel.org/patch/10143637/) however
after realising
this omitted required addresses I added them and resent the patch.

Best regards,
Ian
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-04-11 10:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  4:42 [RESEND PATCH 1/1] drm/i915/glk: Add MODULE_FIRMWARE for Geminilake ianwmorrison
2018-04-11  9:24 ` Jani Nikula
2018-04-11  9:24   ` Jani Nikula
2018-04-11 10:41   ` Ian W MORRISON [this message]
2018-04-11 10:41     ` Ian W MORRISON
2018-04-11 12:27     ` Jani Nikula
2018-04-11 13:04       ` Ian W MORRISON
2018-04-16 22:47       ` Srivatsa, Anusha
2018-04-17  9:02         ` Jani Nikula
2018-04-17  9:02           ` Jani Nikula
2018-04-17 14:14           ` Joonas Lahtinen
2018-04-20  5:47             ` Ian W MORRISON
2018-04-20  7:50               ` Jani Nikula
2018-04-20  7:50                 ` Jani Nikula
2018-04-20  8:25                 ` Ian W MORRISON
2018-04-20  8:25                   ` Ian W MORRISON
2018-04-20 18:03           ` Rodrigo Vivi
2018-04-20 18:03             ` Rodrigo Vivi
2018-04-20 18:30             ` Srivatsa, Anusha
2018-04-20 18:30               ` Srivatsa, Anusha
2018-04-21  1:22               ` Botello Ortega, Luis
2018-04-21  1:22                 ` Botello Ortega, Luis
2018-04-21 22:46                 ` Ian W MORRISON
2018-04-21 22:46                   ` Ian W MORRISON
2018-04-25 23:15                   ` Ian W MORRISON
2018-04-25 23:15                     ` Ian W MORRISON
2018-04-27  9:20                     ` Jani Nikula
2018-04-27  9:20                       ` Jani Nikula
2018-04-30  7:58                       ` Joonas Lahtinen
2018-04-11 10:54 ` ✓ Fi.CI.BAT: success for series starting with [RESEND,1/1] " Patchwork
2018-04-11 12:37 ` ✓ Fi.CI.IGT: " Patchwork

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=CAFXWsS_SvkLvJcibx9LoUw+onN-AAzSLMrRgx3U3hsbMVyty2g@mail.gmail.com \
    --to=ianwmorrison@gmail.com \
    --cc=airlied@linux.ie \
    --cc=anusha.srivatsa@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.wajdeczko@intel.com \
    --cc=rodrigo.vivi@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.