linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Suraj Jitindar Singh <sjitindarsingh@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: mikey@neuling.org, joel@jms.id.au,
	Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Subject: Re: [1/2] powerpc/prom: Remove VLA in prom_check_platform_support()
Date: Thu, 20 Sep 2018 14:21:00 +1000 (AEST)	[thread overview]
Message-ID: <42G3SX12XHz9sCt@ozlabs.org> (raw)
In-Reply-To: <20180905020951.10372-2-sjitindarsingh@gmail.com>

On Wed, 2018-09-05 at 02:09:50 UTC, Suraj Jitindar Singh wrote:
> In prom_check_platform_support() we retrieve and parse the
> "ibm,arch-vec-5-platform-support" property of the chosen node.
> Currently we use a variable length array however to avoid this use an
> array of constant length 8.
> 
> This property is used to indicate the supported options of vector 5
> bytes 23-26 of the ibm,architecture.vec node. Each of these options
> is a pair of bytes, thus for 4 options we have a max length of 8 bytes.
> 
> Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
> Reviewed-by: Joel Stanley <joel@jms.id.au>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/ab91239942a900e209f72488627306

cheers

  parent reply	other threads:[~2018-09-20  4:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05  2:09 [PATCH 0/2] Remove Variable Length Arrays from powerpc code Suraj Jitindar Singh
2018-09-05  2:09 ` [PATCH 1/2] powerpc/prom: Remove VLA in prom_check_platform_support() Suraj Jitindar Singh
2018-09-17  2:37   ` Joel Stanley
2018-09-20  4:21   ` Michael Ellerman [this message]
2018-09-05  2:09 ` [PATCH 2/2] powerpc/pseries: Remove VLA from lparcfg_write() Suraj Jitindar Singh
2018-09-17  2:37   ` Joel Stanley

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=42G3SX12XHz9sCt@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=sjitindarsingh@gmail.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;
as well as URLs for NNTP newsgroup(s).