From: Brendan Higgins <brendanhiggins@google.com>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Patrick Venture <venture@google.com>,
Avi Fishman <avifishman70@gmail.com>,
Joel Stanley <joel@jms.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Nancy Yuen <yuenn@google.com>
Subject: Re: [PATCH v1 1/2] arm: npcm: modify configuration for the NPCM7xx BMC.
Date: Fri, 16 Mar 2018 05:56:04 +0000 [thread overview]
Message-ID: <CAFd5g47AeTtU_uYNOuDKroBwf_FMd+4Z7WgcCM5wyj2e_PEZrQ@mail.gmail.com> (raw)
In-Reply-To: <1521155412-29229-2-git-send-email-tmaimon77@gmail.com>
On Thu, Mar 15, 2018 at 4:16 PM Tomer Maimon <tmaimon77@gmail.com> wrote:
> Modify configuration and MakeFile
> for the Nuvoton NPCM and NPCM7xx BMC.
> Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
> ---
> arch/arm/mach-npcm/Kconfig | 40 +++++++++++-----------------------------
> arch/arm/mach-npcm/Makefile | 4 +++-
> 2 files changed, 14 insertions(+), 30 deletions(-)
<snip>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
WARNING: multiple messages have this Message-ID (diff)
From: brendanhiggins@google.com (Brendan Higgins)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/2] arm: npcm: modify configuration for the NPCM7xx BMC.
Date: Fri, 16 Mar 2018 05:56:04 +0000 [thread overview]
Message-ID: <CAFd5g47AeTtU_uYNOuDKroBwf_FMd+4Z7WgcCM5wyj2e_PEZrQ@mail.gmail.com> (raw)
In-Reply-To: <1521155412-29229-2-git-send-email-tmaimon77@gmail.com>
On Thu, Mar 15, 2018 at 4:16 PM Tomer Maimon <tmaimon77@gmail.com> wrote:
> Modify configuration and MakeFile
> for the Nuvoton NPCM and NPCM7xx BMC.
> Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
> ---
> arch/arm/mach-npcm/Kconfig | 40 +++++++++++-----------------------------
> arch/arm/mach-npcm/Makefile | 4 +++-
> 2 files changed, 14 insertions(+), 30 deletions(-)
<snip>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
next prev parent reply other threads:[~2018-03-16 5:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 23:10 [PATCH v1 0/2] arm: npcm: Modify NPCM7XX machine code Tomer Maimon
2018-03-15 23:10 ` Tomer Maimon
2018-03-15 23:10 ` [PATCH v1 1/2] arm: npcm: modify configuration for the NPCM7xx BMC Tomer Maimon
2018-03-15 23:10 ` Tomer Maimon
2018-03-16 5:56 ` Brendan Higgins [this message]
2018-03-16 5:56 ` Brendan Higgins
2018-03-16 5:56 ` Brendan Higgins
2018-04-05 12:51 ` Arnd Bergmann
2018-04-05 12:51 ` Arnd Bergmann
2018-04-05 12:51 ` Arnd Bergmann
2018-03-15 23:10 ` [PATCH v1 2/2] arm: npcm: Enable L2 Cache in NPCM7xx Tomer Maimon
2018-03-15 23:10 ` Tomer Maimon
2018-03-16 5:52 ` Brendan Higgins
2018-03-16 5:52 ` Brendan Higgins
2018-03-16 5:52 ` Brendan Higgins
2018-03-16 21:51 ` Tomer Maimon
2018-04-05 12:54 ` Arnd Bergmann
2018-04-05 12:54 ` Arnd Bergmann
2018-04-05 12:54 ` Arnd Bergmann
2018-04-05 16:56 ` Tomer Maimon
2018-04-05 20:42 ` Arnd Bergmann
2018-04-05 20:42 ` Arnd Bergmann
2018-04-05 20:42 ` Arnd Bergmann
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=CAFd5g47AeTtU_uYNOuDKroBwf_FMd+4Z7WgcCM5wyj2e_PEZrQ@mail.gmail.com \
--to=brendanhiggins@google.com \
--cc=arnd@arndb.de \
--cc=avifishman70@gmail.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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 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.