All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
	linux-doc@vger.kernel.org, a.zummo@towertech.it,
	John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH 0/2] Documentation, update RTC documentation
Date: Wed, 18 Mar 2015 15:12:29 -0400	[thread overview]
Message-ID: <5509CE1D.20506@redhat.com> (raw)
In-Reply-To: <20150316111048.66dd7f02@lwn.net>



On 03/16/2015 01:10 PM, Jonathan Corbet wrote:
> On Mon, 16 Mar 2015 11:58:53 -0400
> Prarit Bhargava <prarit@redhat.com> wrote:
> 
>> Documentation/rtc.txt is a combination of two files, a real documentation
>> file and a test program.  Splitting these up into two files is a good idea
>> for automated testing.
> 
> Makes sense to me.  If you're going to do that, though, rtctest.c should
> move out of the documentation directory to, probably, somewhere under
> tools/.
> 

Thanks for the input Jon.  I'm going to resubmit this after jstultz' timekeeping
tests get into linux-next or linux.  It looks like my changes will fit nicely on
top of his.  I've tested them locally here and don't see any issues.

http://marc.info/?l=linux-kernel&m=142612122002939&w=2

P.

      reply	other threads:[~2015-03-18 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 15:58 [PATCH 0/2] Documentation, update RTC documentation Prarit Bhargava
2015-03-16 15:58 ` [PATCH 1/2] Documentation, add rtc directory and split up rtc.txt Prarit Bhargava
2015-03-16 15:58 ` [PATCH 2/2] Documentation, update rtctest.c to verify passage of time Prarit Bhargava
2015-03-16 17:10 ` [PATCH 0/2] Documentation, update RTC documentation Jonathan Corbet
2015-03-18 19:12   ` Prarit Bhargava [this message]

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=5509CE1D.20506@redhat.com \
    --to=prarit@redhat.com \
    --cc=a.zummo@towertech.it \
    --cc=corbet@lwn.net \
    --cc=john.stultz@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    /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.