public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Stas Sergeev <stsp@aknet.ru>
Cc: linux-kernel@vger.kernel.org, vojtech@ucw.cz
Subject: Re: [patch 1/2] pcspeaker driver update
Date: Wed, 15 Jun 2005 13:33:38 -0700	[thread overview]
Message-ID: <20050615133338.398febbc.akpm@osdl.org> (raw)
In-Reply-To: <42B056A3.4040202@aknet.ru>

Stas Sergeev <stsp@aknet.ru> wrote:
>
> Andrew Morton wrote:
> >> Attached one is just a clean-up:
> >>  it removes the extern definitions
> >>  for the i8253_lock and i8259A_lock,
> >>  making the use of the appropriate
> >>  headers instead.
> > A nice cleanup to make, however we cannot include asm/timer.h from generic
> > code, because only a few architectures have such a file.
> OK, what a bugger...
> Does the attached one look any better?

Well not really - for example you now have drivers/input/joystick/analog.c
including asm/8253pit.h, which not all architectures implement.

The basic problem is that we have generic code referring to an x86-specific
lock inside `#ifdef __i386__'.

Perhaps what you could do is to declare those locks in
include/asm-i386/hardirq.h and then make sure that all the relevant files
include <linux/hardirq.h>.  That's a bit of an abuse of hardirq.h, but we
don't have a generic "platform.h" place to put things like this.

If abusing hardirq.h offends you then you could make sure that all
architectures implement asm/rtc.h (most already do) (just copy
include/asm-alpha/rtc.h) and put the declarations in
include/asm-i386/rtc.h, which is more appropriate.

Whichever way you go, please check that x86_64 works OK too.

  reply	other threads:[~2005-06-15 20:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 18:39 [patch 1/2] pcspeaker driver update Stas Sergeev
2005-06-14 20:45 ` Andrew Morton
2005-06-15 16:26   ` Stas Sergeev
2005-06-15 20:33     ` Andrew Morton [this message]
2005-06-16  3:53       ` Stas Sergeev

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=20050615133338.398febbc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stsp@aknet.ru \
    --cc=vojtech@ucw.cz \
    /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