All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <david@lechnology.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Sekhar Nori <nsekhar@ti.com>,
	Kevin Hilman <khilman@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v2 02/12] clocksource: davinci-timer: new driver
Date: Mon, 4 Feb 2019 20:37:47 -0600	[thread overview]
Message-ID: <e47ad813-6469-85c2-e493-af075cd084b4@lechnology.com> (raw)
In-Reply-To: <20190204171757.32073-3-brgl@bgdev.pl>

On 2/4/19 11:17 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> Currently the clocksource and clockevent support for davinci platforms
> lives in mach-davinci. It hard-codes many things, used global variables,

s/used/uses/

> implements functionalities unused by any platform and has code fragments
> scattered across many (often unrelated) files.
> 

WARNING: multiple messages have this Message-ID (diff)
From: David Lechner <david@lechnology.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Sekhar Nori <nsekhar@ti.com>,
	Kevin Hilman <khilman@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v2 02/12] clocksource: davinci-timer: new driver
Date: Mon, 4 Feb 2019 20:37:47 -0600	[thread overview]
Message-ID: <e47ad813-6469-85c2-e493-af075cd084b4@lechnology.com> (raw)
In-Reply-To: <20190204171757.32073-3-brgl@bgdev.pl>

On 2/4/19 11:17 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> 
> Currently the clocksource and clockevent support for davinci platforms
> lives in mach-davinci. It hard-codes many things, used global variables,

s/used/uses/

> implements functionalities unused by any platform and has code fragments
> scattered across many (often unrelated) files.
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-02-05  2:37 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 17:17 [PATCH v2 00/12] ARM: davinci: modernize the timer support Bartosz Golaszewski
2019-02-04 17:17 ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 01/12] ARM: dts: da850: fix interrupt numbers for clocksource Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-05  1:18   ` David Lechner
2019-02-05  1:18     ` David Lechner
2019-02-08 13:09     ` Sekhar Nori
2019-02-08 13:09       ` Sekhar Nori
2019-02-08 13:09       ` Sekhar Nori
2019-02-04 17:17 ` [PATCH v2 02/12] clocksource: davinci-timer: new driver Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-05  2:13   ` David Lechner
2019-02-05  2:13     ` David Lechner
2019-02-05  2:37   ` David Lechner [this message]
2019-02-05  2:37     ` David Lechner
2019-02-08 13:24   ` Sekhar Nori
2019-02-08 13:24     ` Sekhar Nori
2019-02-08 13:24     ` Sekhar Nori
2019-02-04 17:17 ` [PATCH v2 03/12] ARM: davinci: enable the clocksource driver for DT mode Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-05  2:16   ` David Lechner
2019-02-05  2:16     ` David Lechner
2019-02-04 17:17 ` [PATCH v2 04/12] ARM: davinci: WARN_ON() if clk_get() fails Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-05  2:18   ` David Lechner
2019-02-05  2:18     ` David Lechner
2019-02-26 12:08     ` Bartosz Golaszewski
2019-02-26 12:08       ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 05/12] ARM: davinci: da850: switch to using the clocksource driver Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-05  2:35   ` David Lechner
2019-02-05  2:35     ` David Lechner
2019-02-08 12:06   ` Sekhar Nori
2019-02-08 12:06     ` Sekhar Nori
2019-02-08 12:06     ` Sekhar Nori
2019-02-08 12:34     ` Bartosz Golaszewski
2019-02-08 12:34       ` Bartosz Golaszewski
2019-02-08 12:37       ` Sekhar Nori
2019-02-08 12:37         ` Sekhar Nori
2019-02-08 12:47         ` Bartosz Golaszewski
2019-02-08 12:47           ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 06/12] ARM: davinci: da830: " Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-05  2:36   ` David Lechner
2019-02-05  2:36     ` David Lechner
2019-02-08 12:23   ` Sekhar Nori
2019-02-08 12:23     ` Sekhar Nori
2019-02-08 12:23     ` Sekhar Nori
2019-02-08 12:46     ` Bartosz Golaszewski
2019-02-08 12:46       ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 07/12] ARM: davinci: move timer definitions to davinci.h Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 08/12] ARM: davinci: dm355: switch to using the clocksource driver Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-08 12:34   ` Sekhar Nori
2019-02-08 12:34     ` Sekhar Nori
2019-02-08 12:34     ` Sekhar Nori
2019-02-26 12:09     ` Bartosz Golaszewski
2019-02-26 12:09       ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 09/12] ARM: davinci: dm365: " Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 10/12] ARM: davinci: dm644x: " Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 11/12] ARM: davinci: dm646x: " Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski
2019-02-04 17:17 ` [PATCH v2 12/12] ARM: davinci: remove legacy timer support Bartosz Golaszewski
2019-02-04 17:17   ` Bartosz Golaszewski

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=e47ad813-6469-85c2-e493-af075cd084b4@lechnology.com \
    --to=david@lechnology.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nsekhar@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    /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.