All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nicolae Rosia <Nicolae_Rosia@mentor.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP2+: avoid NULL pointer dereference
Date: Mon, 7 Nov 2016 16:25:06 -0700	[thread overview]
Message-ID: <20161107232505.GG2428@atomide.com> (raw)
In-Reply-To: <1477993765-9980-1-git-send-email-Nicolae_Rosia@mentor.com>

* Nicolae Rosia <Nicolae_Rosia@mentor.com> [161101 02:50]:
> For OMAP4, volt_data is set in omap44xx_voltagedomains_init.
> If the SoC is neither OMAP443X or OMAP446X, we end up with a
> NULL in volt_data which causes a kernel oops.
> This is the case when booting OMAP4470.

Thanks applying into omap-for-v4.9/fixes.

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: avoid NULL pointer dereference
Date: Mon, 7 Nov 2016 16:25:06 -0700	[thread overview]
Message-ID: <20161107232505.GG2428@atomide.com> (raw)
In-Reply-To: <1477993765-9980-1-git-send-email-Nicolae_Rosia@mentor.com>

* Nicolae Rosia <Nicolae_Rosia@mentor.com> [161101 02:50]:
> For OMAP4, volt_data is set in omap44xx_voltagedomains_init.
> If the SoC is neither OMAP443X or OMAP446X, we end up with a
> NULL in volt_data which causes a kernel oops.
> This is the case when booting OMAP4470.

Thanks applying into omap-for-v4.9/fixes.

Tony

  reply	other threads:[~2016-11-07 23:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-01  9:49 [PATCH] ARM: OMAP2+: avoid NULL pointer dereference Nicolae Rosia
2016-11-01  9:49 ` Nicolae Rosia
2016-11-07 23:25 ` Tony Lindgren [this message]
2016-11-07 23:25   ` Tony Lindgren

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=20161107232505.GG2428@atomide.com \
    --to=tony@atomide.com \
    --cc=Nicolae_Rosia@mentor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@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.