Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Qiang Zhao <qiang.zhao@nxp.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: fsl-dspi: fix NULL pointer dereference
Date: Fri, 30 Oct 2020 15:14:25 +0200	[thread overview]
Message-ID: <20201030131425.b2c3t3n4v6i67yfv@skbuf> (raw)
In-Reply-To: <VE1PR04MB676878E41EB6E44B325A9C3A91150@VE1PR04MB6768.eurprd04.prod.outlook.com>

On Fri, Oct 30, 2020 at 02:04:06AM +0000, Qiang Zhao wrote:
> I saw the patch, it just fix the issue when the kernel are booted up.
> But there still have the issue when the driver suspend and resume. 

I see, sorry, I only paid attention to the commit message since it
wasn't explicit that it is about the suspend/resume case. Let me look
closer at the patch.

  reply	other threads:[~2020-10-30 13:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  8:40 [PATCH] spi: fsl-dspi: fix NULL pointer dereference Qiang Zhao
2020-10-29 11:03 ` Vladimir Oltean
2020-10-30  2:04   ` Qiang Zhao
2020-10-30 13:14     ` Vladimir Oltean [this message]
2020-10-30 13:02 ` Mark Brown
2020-11-02  2:01   ` Qiang Zhao
2020-10-30 13:18 ` Vladimir Oltean
2020-11-02  2:19   ` Qiang Zhao
2020-11-02 11:17     ` Vladimir Oltean
2020-11-04 20:43 ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2020-09-27 22:43 Michael Walle
2020-09-27 23:27 ` Vladimir Oltean
2020-09-28  7:29   ` Krzysztof Kozlowski
2020-09-28  7:36     ` Krzysztof Kozlowski
2020-09-28  7:46     ` Michael Walle
2020-09-28  8:12       ` Krzysztof Kozlowski
2020-09-28  8:04   ` Sascha Hauer

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=20201030131425.b2c3t3n4v6i67yfv@skbuf \
    --to=olteanv@gmail.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=qiang.zhao@nxp.com \
    /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