linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Gordon Stanton <coder101@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] must fix generic_serial .c
Date: Sat, 6 Sep 2003 21:38:30 +0200	[thread overview]
Message-ID: <20030906193830.GD14436@fs.tum.de> (raw)
In-Reply-To: <20030901062643.14448.qmail@linuxmail.org>

On Mon, Sep 01, 2003 at 02:26:43PM +0800, Gordon Stanton wrote:

> Hi,

Hi Gordon,

>   While trying to get most drivers in the kernel to compile, I had to skip a lot of the older ones that use cli() and sti() since deep knowledge is needed to fix those. Because of this I am asking that someone would please fix generic_serial.c in drivers/char and document in a HOWTO on the steps they took and the reasons behind it. This would help more people to be able to understand and fix a lot of the other drivers with the cli/sti problem. Even if the it wasn't generic_serial.c but one of the other serial drivers with the same problem, it still would be very instructive and help other to improve the kernel quicker. 

it's a known problem that generic_serial doesn't compile in SMP kernels 
due to cli/sti problems.

Documentation/cli-sti-removal.txt already documents how to fix such 
drivers (although it's usually non-trivial).

> Gordon

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2003-09-06 19:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-01  6:26 [RFC] must fix generic_serial .c Gordon Stanton
2003-09-06 19:38 ` Adrian Bunk [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=20030906193830.GD14436@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=coder101@linuxmail.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).