Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH v2 2/4] clk: sunxi-ng: add support for V3s CCU
Date: Thu, 19 Jan 2017 16:41:28 +0100	[thread overview]
Message-ID: <20170119154128.hzhggymgg7uczpfo@lukather> (raw)
In-Reply-To: <20170117200213.27eGY8hi@smtp3h.mail.yandex.net>

On Wed, Jan 18, 2017 at 01:02:03AM +0800, Icenowy Zheng wrote:
> 
> 2017?1?17? 17:04? Maxime Ripard <maxime.ripard@free-electrons.com>???
> >
> > Hi, 
> >
> > On Tue, Jan 17, 2017 at 02:01:14AM +0800, Icenowy Zheng wrote: 
> > > V3s has a similar but cut-down CCU to H3. 
> > > 
> > > Add support for it. 
> > > 
> > > Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz> 
> > > --- 
> >
> > Output from checkpatch: 
> > total: 5 errors, 2 warnings, 3 checks, 857 lines checked 
> >
> > > I think I should make a comparsion between V3s and H3 CCU here: 
> > > (I won't mention the missing/added clocks here, only list conflicting clocks) 
> >
> > That should be in your commit log. 
> 
> I think it can be easily get by a diff command :-)
> 
> And we do not have the tradition to describe clock difference in
> commit log, is it right?

In very low details, no, but still having the big picture is a good
idea.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170119/799557e0/attachment-0001.sig>

           reply	other threads:[~2017-01-19 15:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170117200213.27eGY8hi@smtp3h.mail.yandex.net>]

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=20170119154128.hzhggymgg7uczpfo@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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