From: John Stultz <john.stultz@linaro.org>
To: Marcelo Roberto Jimenez <mroberto@cpti.cetuc.puc-rio.br>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
linux@arm.linux.org.uk, tglx@linutronix.de, a.zummo@towertech.it
Subject: Re: [PATCH 1/4] RTC: Include information about UIE and PIE in RTC driver proc.
Date: Thu, 10 Feb 2011 15:06:13 -0800 [thread overview]
Message-ID: <1297379173.1865.1.camel@localhost> (raw)
In-Reply-To: <1297113368-27174-2-git-send-email-mroberto@cpti.cetuc.puc-rio.br>
On Mon, 2011-02-07 at 19:16 -0200, Marcelo Roberto Jimenez wrote:
> Generic RTC code is always able to provide the necessary information
> about update and periodic interrupts. This patch add such information to
> the proc interface.
This seems to be mostly formatting changes. Are you sure we wont' break
applications expecting the existing format?
thanks
-john
next prev parent reply other threads:[~2011-02-10 23:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 21:16 [PATCH 0/4] RTC: Updates for RTC Marcelo Roberto Jimenez
2011-02-07 21:16 ` [PATCH 1/4] RTC: Include information about UIE and PIE in RTC driver proc Marcelo Roberto Jimenez
2011-02-10 23:06 ` John Stultz [this message]
2011-02-11 12:34 ` Marcelo Roberto Jimenez
2011-02-07 21:16 ` [PATCH 2/4] RTC: Remove UIE and PIE information from the sa1100 " Marcelo Roberto Jimenez
2011-02-07 21:16 ` [PATCH 3/4] RTC: Fix the cross interrupt issue on rtc-test Marcelo Roberto Jimenez
2011-02-07 21:16 ` [PATCH 4/4] RTC: sa1100: Update the sa1100 RTC driver Marcelo Roberto Jimenez
2011-02-07 22:09 ` [PATCH 0/4] RTC: Updates for RTC Russell King - ARM Linux
2011-02-10 23:18 ` John Stultz
2011-02-11 13:57 ` [rtc-linux] " Marcelo Roberto Jimenez
-- strict thread matches above, loose matches on Subject: below --
2011-02-11 13:50 [PATCH 1/4] RTC: Include information about UIE and PIE in RTC driver proc Marcelo Roberto Jimenez
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=1297379173.1865.1.camel@localhost \
--to=john.stultz@linaro.org \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mroberto@cpti.cetuc.puc-rio.br \
--cc=rtc-linux@googlegroups.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox