linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/5] rtc: mxc_rtc: Driver rework
Date: Sun, 30 Jun 2013 10:05:46 +0200	[thread overview]
Message-ID: <20130630080546.GS516@pengutronix.de> (raw)
In-Reply-To: <1372541615.220890134@f402.i.mail.ru>

On Sun, Jun 30, 2013 at 01:33:35AM +0400, Alexander Shiyan wrote:
> > > On Sat, Jun 29, 2013 at 12:40:40PM +0400, Alexander Shiyan wrote:
> > > > This patch rework mxc_rtc driver.
> > > > Major changes have been made:
> > > > - Added second clock support (optional) which permit module functionality.
> > > > - Implemented support for periodic interrupts.
> > > > - Some code have been optimized.
> > > 
> > > You won't get any further with this if you don't listen to comments.
> > > 
> > > We're at v3 and Still this patch combines many totally unrelated changes
> > > in a single patch. This was noted by Shawn and more detailed by myself.
> > 
> > Where Sascha?
> > v3 is so different than v2. Can you inline your comments in v3?

I just did that.

> 
> At the moment, the driver does not work at all, even for a boards which declared.
> I do not understand the issue of making changes if we can correct this situation 
> Please fix me.
> Once again, now driver not work at all .....

If the driver is really so broken and ugly that it can't be fixed or
only with a huge amount of work, then your option would be to replace it
completely and clearly say why you think it's broken and why we need a
new driver.

I don't think that's the case. The driver has it's deficiencies, but
they can be fixed. Many of your changes are fine, but it's really 5-10
patches you have thrown into a single patch.
This is simply not nice to people reviewing it.

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 |

  reply	other threads:[~2013-06-30  8:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29  8:40 [PATCH v3 1/5] rtc: mxc_rtc: Driver rework Alexander Shiyan
2013-06-29  8:40 ` [PATCH v3 2/5] rtc: mxc_rtc: Cleanup code Alexander Shiyan
2013-06-29  8:40 ` [PATCH v3 4/5] rtc: mxc_rtc: Add DT support Alexander Shiyan
2013-06-29  8:40 ` [PATCH v3 3/5] ARM: imx: Using proper clocks for RTC driver Alexander Shiyan
2013-06-29  8:40 ` [PATCH v3 5/5] ARM: imx: move i.MX1/21/27 RTC clk lookup into DT Alexander Shiyan
2013-06-29 12:14 ` [PATCH v3 1/5] rtc: mxc_rtc: Driver rework Sascha Hauer
2013-06-29 21:01   ` Re[2]: " Alexander Shiyan
2013-06-29 21:33     ` Re[3]: " Alexander Shiyan
2013-06-30  8:05       ` Sascha Hauer [this message]
2013-06-30  9:10         ` Re[2]: " Alexander Shiyan
2013-06-30 10:16           ` Sascha Hauer
2013-06-30  7:52 ` Sascha Hauer
2013-06-30  8:26   ` Re[2]: " Alexander Shiyan
2013-06-30  8:42     ` [PATCH v3 1/5] rtc: mxc_rtc: Driver re work Lothar Waßmann
2013-06-30  8:45       ` Re[4]: " Alexander Shiyan

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=20130630080546.GS516@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).