public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Steven Rostedt <srostedt@stny.rr.com>
Cc: duwe@informatik.uni-erlangen.de,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mc146818rtc.h for user land programs (2.4.10)
Date: Wed, 26 Sep 2001 09:33:49 -0700	[thread overview]
Message-ID: <3BB2036D.A72C1C25@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109261152100.5923-100000@localhost.localdomain>

Steven Rostedt wrote:
> 
> The following patch is for linux-2.4.10
> This is needed for user land programs to use the
> mc146818rtc.h header.
> 
> --- include/linux/mc146818rtc.h.orig    Wed Sep 26 23:43:00 2001
> +++ include/linux/mc146818rtc.h Wed Sep 26 23:43:25 2001
> @@ -16,7 +16,9 @@
>  #include <linux/spinlock.h>            /* spinlock_t */
>  #include <asm/mc146818rtc.h>           /* register access macros */
> 
> +#ifdef __KERNEL__
>  extern spinlock_t rtc_lock;            /* serialize CMOS RAM access */
> +#endif

I can see arguing with Alan about the inclusion of linux-kernel headers
in some cases, but I don't see anything in this file that looks like a
user-space program could use.  Which part of this file do the user
space programs need?

Ben


-- 
Ben Greear <greearb@candelatech.com>          <Ben_Greear@excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  parent reply	other threads:[~2001-09-26 16:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 16:19 [PATCH] mc146818rtc.h for user land programs (2.4.10) Steven Rostedt
2001-09-26 16:26 ` Alan Cox
2001-09-26 16:33 ` Ben Greear [this message]
2001-09-26 17:40   ` Tim Hockin
2001-09-26 18:20     ` Steven Rostedt
2001-09-27 11:48   ` Torsten Duwe

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=3BB2036D.A72C1C25@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=duwe@informatik.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@stny.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox