mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Simmons <jsimmons@linux-fbdev.org>
To: Eric Gillespie <viking@flying-brick.caverock.net.nz>
Cc: Andrew Morton <andrewm@uow.edu.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: More about 2.4.3 timer problems
Date: Wed, 4 Apr 2001 20:06:07 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.31.0104042004280.1580-100000@linux.local> (raw)


>Err, tried the patch you recommended me to apply to the 2.4.3 source code
>(not the 2.4.3-pre6), but everything else started complaining it couldn't
>see printk() any more.  Any advice?  Thanks...

Can you tell us your hardware configuration and your kernel configuration.
What do you mean it couldn't see printk any more?

MS: (n) 1. A debilitating and surprisingly widespread affliction that
renders the sufferer barely able to perform the simplest task. 2. A disease.

James Simmons  [jsimmons@linux-fbdev.org]               ____/|
fbdev/console/gfx developer                             \ o.O|
http://www.linux-fbdev.org                               =(_)=
http://linuxgfx.sourceforge.net                            U
http://linuxconsole.sourceforge.net


             reply	other threads:[~2001-04-05  3:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-05  3:06 James Simmons [this message]
2001-04-05  4:21 ` Eric Gillespie
2001-04-05  6:46   ` [QUESTION] 2.4.3: hotplug_path unresolved in usbcore? Ryan Mack
2001-04-05 12:08     ` Bart Trojanowski
     [not found] <3AC99E08.3C126F90@uow.edu.au>
2001-04-04  7:42 ` More about 2.4.3 timer problems Eric Gillespie
  -- strict thread matches above, loose matches on Subject: below --
2001-04-03  0:56 Eric Gillespie
2001-04-03  2:52 ` Andrew Morton
2001-04-03  4:55   ` viking
2001-04-03 12:33 ` Alan Cox

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=Pine.LNX.4.31.0104042004280.1580-100000@linux.local \
    --to=jsimmons@linux-fbdev.org \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viking@flying-brick.caverock.net.nz \
    /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

all inboxes | Powered by JetHome®