All of lore.kernel.org
 help / color / mirror / Atom feed
From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1 0/6] rtc: rtc-isl12057: fixes and alarm support
Date: Wed, 26 Nov 2014 21:10:29 +0100	[thread overview]
Message-ID: <87egsp205m.fsf@natisbad.org> (raw)
In-Reply-To: <20141126115345.a3ef26c9fef0c388cbb6e6ee@linux-foundation.org> (Andrew Morton's message of "Wed, 26 Nov 2014 11:53:45 -0800")

Hi Andrew,

Andrew Morton <akpm@linux-foundation.org> writes:

>> > akpm already applied the series, doesn't he?
>> 
>> I am not really familiar w/ -mm tree workflow. It was not clear to me
>> whether it was sitting in -mm tree waiting for reviewed-by and
>> acked-by.
>
> -mm is a collection of several hundred trees (most of which are empty
> at a particular time).  The workflow depends on which tree we're
> talking about!
>
> For RTC patches I attempt to review them myself but I'm by no means an
> expert on RTC, so I'm careful to cc various people who I think might
> help with review and test.  Often people do this.  Generally when they
> don't, the patches are sufficiently obvious for me to proceed under my
> own steam.  If something breaks (this is rare), the number of people
> who are affected is usually quite small and they tend to be system
> developers who can fix it up for us anyway.

Thanks for the explanation.

Cheers,

a+

WARNING: multiple messages have this Message-ID (diff)
From: arno@natisbad.org (Arnaud Ebalard)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
	"Mark Brown" <broonie@kernel.org>,
	"Jason Cooper" <jason@lakedaemon.net>,
	"Alessandro Zummo" <a.zummo@towertech.it>,
	"Peter Huewe" <peter.huewe@infineon.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Thierry Reding" <treding@nvidia.com>,
	devicetree@vger.kernel.org, rtc-linux@googlegroups.com,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Stephen Warren" <swarren@wwwdotorg.org>,
	linux-doc@vger.kernel.org,
	"Rob Herring" <rob.herring@calxeda.com>,
	"Jason Gunthorpe" <jgunthorpe@obsidianresearch.com>,
	linux-arm-kernel@lists.infradead.org,
	"Rob Landley" <rob@landley.net>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Grant Likely" <grant.likely@linaro.org>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Mark Rutland" <mark.rutland@arm.com>
Subject: Re: [PATCHv1 0/6] rtc: rtc-isl12057: fixes and alarm support
Date: Wed, 26 Nov 2014 21:10:29 +0100	[thread overview]
Message-ID: <87egsp205m.fsf@natisbad.org> (raw)
In-Reply-To: <20141126115345.a3ef26c9fef0c388cbb6e6ee@linux-foundation.org> (Andrew Morton's message of "Wed, 26 Nov 2014 11:53:45 -0800")

Hi Andrew,

Andrew Morton <akpm@linux-foundation.org> writes:

>> > akpm already applied the series, doesn't he?
>> 
>> I am not really familiar w/ -mm tree workflow. It was not clear to me
>> whether it was sitting in -mm tree waiting for reviewed-by and
>> acked-by.
>
> -mm is a collection of several hundred trees (most of which are empty
> at a particular time).  The workflow depends on which tree we're
> talking about!
>
> For RTC patches I attempt to review them myself but I'm by no means an
> expert on RTC, so I'm careful to cc various people who I think might
> help with review and test.  Often people do this.  Generally when they
> don't, the patches are sufficiently obvious for me to proceed under my
> own steam.  If something breaks (this is rare), the number of people
> who are affected is usually quite small and they tend to be system
> developers who can fix it up for us anyway.

Thanks for the explanation.

Cheers,

a+

  reply	other threads:[~2014-11-26 20:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14 23:06 [PATCHv1 0/6] rtc: rtc-isl12057: fixes and alarm support Arnaud Ebalard
2014-11-14 23:06 ` Arnaud Ebalard
2014-11-14 23:06 ` [PATCHv1 1/6] rtc: rtc-isl12057: fix masking of register values Arnaud Ebalard
2014-11-14 23:06   ` Arnaud Ebalard
2014-11-14 23:06 ` [PATCHv1 2/6] rtc: rtc-isl12057: add support for century bit Arnaud Ebalard
2014-11-14 23:06   ` Arnaud Ebalard
2014-11-14 23:06 ` [PATCHv1 3/6] rtc: rtc-isl12057: add proper handling of oscillator failure bit Arnaud Ebalard
2014-11-14 23:06   ` Arnaud Ebalard
2014-11-14 23:07 ` [PATCHv1 4/6] rtc: rtc-isl12057: fix isil vs isl naming for intersil Arnaud Ebalard
2014-11-14 23:07   ` Arnaud Ebalard
2014-12-10 21:30   ` [rtc-linux] " Andrew Morton
2014-12-10 21:30     ` Andrew Morton
2014-12-11 19:59     ` Arnaud Ebalard
2014-12-11 19:59       ` Arnaud Ebalard
2014-11-14 23:07 ` [PATCHv1 5/6] rtc: rtc-isl12057: report error code upon failure in dev_err() calls Arnaud Ebalard
2014-11-14 23:07   ` Arnaud Ebalard
2014-11-14 23:07 ` [PATCHv1 6/6] rtc: rtc-isl12057: add alarm support to Intersil ISL12057 RTC driver Arnaud Ebalard
2014-11-14 23:07   ` Arnaud Ebalard
2014-11-27  9:23   ` Uwe Kleine-König
2014-11-27  9:23     ` Uwe Kleine-König
2014-12-01  8:07     ` Arnaud Ebalard
2014-12-01  8:07       ` Arnaud Ebalard
2014-12-01 20:11     ` Arnaud Ebalard
2014-12-01 20:11       ` Arnaud Ebalard
2014-12-02  8:26       ` Uwe Kleine-König
2014-12-02  8:26         ` Uwe Kleine-König
2014-11-26 18:35 ` [PATCHv1 0/6] rtc: rtc-isl12057: fixes and alarm support Arnaud Ebalard
2014-11-26 18:35   ` Arnaud Ebalard
2014-11-26 18:48   ` Uwe Kleine-König
2014-11-26 18:48     ` Uwe Kleine-König
2014-11-26 19:02     ` Mark Brown
2014-11-26 19:02       ` Mark Brown
2014-11-26 19:28     ` Arnaud Ebalard
2014-11-26 19:28       ` Arnaud Ebalard
2014-11-26 19:53       ` Andrew Morton
2014-11-26 19:53         ` Andrew Morton
2014-11-26 20:10         ` Arnaud Ebalard [this message]
2014-11-26 20:10           ` Arnaud Ebalard
2014-11-26 19:46     ` Andrew Morton
2014-11-26 19:46       ` Andrew Morton

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=87egsp205m.fsf@natisbad.org \
    --to=arno@natisbad.org \
    --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 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.