From: Rob Herring <robh@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: Tali Perry <tali.perry1@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Avi Fishman <avifishman70@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
Rick Altherr <raltherr@google.com>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Nancy Yuen <yuenn@google.com>,
Patrick Venture <venture@google.com>
Subject: Re: [PATCH v2 1/1] clk: npcm750: update text with fixed clocks
Date: Mon, 19 Feb 2018 08:49:05 -0600 [thread overview]
Message-ID: <20180219144905.bfrycjnas7dcuo34@rob-hp-laptop> (raw)
In-Reply-To: <CAFd5g44gBJp0-mYEWGdyiA67BCi2pZWAG2bYPS-WdJEwH1oA5A@mail.gmail.com>
On Thu, Feb 15, 2018 at 02:38:12PM -0800, Brendan Higgins wrote:
> On Thu, Feb 15, 2018 at 5:39 AM, Tali Perry <tali.perry1@gmail.com> wrote:
> >
> > Signed-off-by: Tali Perry <tali.perry1@gmail.com>
> >
> <snip>
>
> I think this should probably be rolled into [PATCH v2 1/1] npcm750: add fixed
> clocks (moved from drivers/clk/clk-npcm7xx.c):
> https://www.spinics.net/lists/arm-kernel/msg634678.html
No, binding docs, dts files and driver code should all be separate
patches.
Rob
next prev parent reply other threads:[~2018-02-19 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 13:39 [PATCH v2 0/1] *clk: npcm750: add clock header to patch, fix typos and content in dt-binding txt Tali Perry
2018-02-15 13:39 ` [PATCH v2 1/1] clk: npcm750: update text with fixed clocks Tali Perry
2018-02-15 22:38 ` Brendan Higgins
2018-02-19 14:49 ` Rob Herring [this message]
2018-02-21 4:47 ` Brendan Higgins
2018-02-21 13:23 ` Rob Herring
2018-02-21 18:22 ` Brendan Higgins
2018-02-19 14:56 ` Rob Herring
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=20180219144905.bfrycjnas7dcuo34@rob-hp-laptop \
--to=robh@kernel.org \
--cc=avifishman70@gmail.com \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=raltherr@google.com \
--cc=tali.perry1@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®