linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: skiboot@lists.ozlabs.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH (skiboot)] dt: add /cpus/ibm,powerpc-cpu-features device tree bindings
Date: Sat, 3 Feb 2018 14:31:09 +1000	[thread overview]
Message-ID: <20180203143109.29dad410@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20180203042732.27980-1-npiggin@gmail.com>

On Sat,  3 Feb 2018 14:27:32 +1000
Nicholas Piggin <npiggin@gmail.com> wrote:


> diff --git a/core/cpufeatures.c b/core/cpufeatures.c
> new file mode 100644
> index 000000000..ca9df91f0
> --- /dev/null
> +++ b/core/cpufeatures.c
> @@ -0,0 +1,932 @@
> +/* Copyright 2017 IBM Corp.
> + *
> + * Licensed under the Apache License, Version 2.0 (the "License");
> + * you may not use this file except in compliance with the License.
> + * You may obtain a copy of the License at
> + *
> + * 	http://www.apache.org/licenses/LICENSE-2.0
> + *
> + * Unless required by applicable law or agreed to in writing, software
> + * distributed under the License is distributed on an "AS IS" BASIS,
> + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> + * implied.
> + * See the License for the specific language governing permissions and
> + * limitations under the License.
> + */
> +
> +/*
> + * This file deals with setup of /cpus/ibm,powerpc-cpu-features dt
> + */
> +
> +#include <skiboot.h>
> +#include <cpu.h>
> +#include <processor.h>
> +#include <ccan/str/str.h>
> +#include <device.h>
> +
> +#define DEBUG

Sorry, didn't send the right version after testing. This line should be
deleted before going upstream.

Thanks,
Nick

  reply	other threads:[~2018-02-03  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03  4:27 [PATCH (skiboot)] dt: add /cpus/ibm, powerpc-cpu-features device tree bindings Nicholas Piggin
2018-02-03  4:31 ` Nicholas Piggin [this message]
2018-02-03 15:36 ` Segher Boessenkool
2018-02-05  1:26   ` Nicholas Piggin
2018-02-05 14:41     ` Segher Boessenkool

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=20180203143109.29dad410@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=skiboot@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).