mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 0/9] at91: Support PMC clock bindings
Date: Mon, 18 Feb 2019 09:10:14 +0100	[thread overview]
Message-ID: <20190218081014.ea4m7vcsndojdgwf@pengutronix.de> (raw)
In-Reply-To: <20190217161609.11305-1-sam@ravnborg.org>

On Sun, Feb 17, 2019 at 05:16:00PM +0100, Sam Ravnborg wrote:
> The following patchset add supports for the PMC clk
> bindings for at91.
> The patchset was tested on:
> - at91sam9264ek - DT enabled
> - sama5d4-xplained - non DT
> 
> The patchset includes sama5d2.c which is not used today.
> I have a sama5d27-som1-ek board that I hope to find time to work
> with and then this will be needed.
> 
> Patch 4-8 add drivers but do not wire then into the build.
> This was done to somehow ease review of the final patch.
> Patches are rather big but trying to split them up more
> than already done seems not worth it.
> 
> Patch was made on top of:
> 12cd92023788fdc67ad72c6e7d96251a6234ca3e ("Merge branch 'for-next/rpi' into next")
> 
> On stray patch sneaked in - to kill a warning.
> 
> The patchset triggers some checkpatch warnings:
> - SPDX, the barebox variant of checkpatch is missing support for these (anyone?)
> - Too long lines. As code is copied from the kernel I left them as-is
> 
> Comments/testing very welcome!

Applied, thanks. Since AT91 is broken currently I applied it to master.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2019-02-18  8:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 16:16 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 1/9] clocksource: Do not mix depends and select for ATMEL_PIT Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 2/9] arm: at91: fix at91_configure_usart6 warning Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 3/9] arm: at91: add SOC_SAMA5{D3,D4} Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 4/9] clk: at91: add at91sam9260 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 5/9] clk: at91: add at91sam9rl Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 6/9] clk: at91: add at91sam9x5 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 7/9] clk: at91: add sama5d2 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 8/9] clk: at91: add sama5d4 Sam Ravnborg
2019-02-17 16:16 ` [PATCH v2 9/9] clk: at91: update to new bindings Sam Ravnborg
2019-02-17 18:44 ` [PATCH v2 0/9] at91: Support PMC clock bindings Sam Ravnborg
2019-02-17 21:32   ` Ladislav Michl
2019-02-17 21:53     ` Sam Ravnborg
2019-02-18  8:10 ` Sascha Hauer [this message]
2019-02-18 19:59   ` Sam Ravnborg
2019-02-19  9:05     ` Sascha Hauer
2019-02-19 10:01       ` Sam Ravnborg
2019-02-19 10:53         ` Sascha Hauer
2019-02-19 10:05       ` Ladislav Michl

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=20190218081014.ea4m7vcsndojdgwf@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=sam@ravnborg.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