public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Miguel Borges de Freitas <miguelborgesdefreitas@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	rmk+kernel@armlinux.org.uk
Subject: Re: [Patch include request] ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe
Date: Mon, 4 May 2020 11:58:32 +0200	[thread overview]
Message-ID: <20200504095832.GA1277837@kroah.com> (raw)
In-Reply-To: <CAC4G8N75VkqDug9AmhvMQnXr8bOvC9cu_jUwZVUKwpvWr6pO5A@mail.gmail.com>

On Fri, May 01, 2020 at 09:23:49PM +0100, Miguel Borges de Freitas wrote:
> Dear all,
> 
> This is a request to backport b7dc7205b2ae6b6c9d9cfc3e47d6f08da8647b10
> (Arm: dts:  imx6qdl-sr-som-ti: indicate powering off wifi is safe),
> already in Linus tree
> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/imx6qdl-sr-som-ti.dtsi?h=v5.7-rc3&id=b7dc7205b2ae6b6c9d9cfc3e47d6f08da8647b10)
> to LTS kernel 5.4 and to stable 5.6.8.
> 
> Reasoning:
> 
> Changes to the wlcore driver during Kernel 5.x development, made the
> Cubox-i with the IMX SOM v1.5 (which includes.a TI Wilink 8 wifi
> chipset) not power the wireless interface on boot leaving it
> completely unusable. This happens since at least kernel 5.3 (older one
> I tested) and affects the current stable and LTS latest kernels. The
> linked commit, already in linux mainline, restores the wifi
> functionality.
> 
> Thanks in advance,

Now queued up, thanks.

greg k-h

  reply	other threads:[~2020-05-04  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 20:23 [Patch include request] ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe Miguel Borges de Freitas
2020-05-04  9:58 ` Greg KH [this message]
2020-05-04 10:13   ` Russell King - ARM Linux admin

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=20200504095832.GA1277837@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguelborgesdefreitas@gmail.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --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