public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: torvalds@transmeta.com, zwane@linuxpower.ca,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5 patch] remove EXPORT_NO_SYMBOLS from amd7xx_tco
Date: Wed, 5 Mar 2003 22:57:02 -0100	[thread overview]
Message-ID: <20030305235644.GA23028@suse.de> (raw)
In-Reply-To: <20030305221302.GN20423@fs.tum.de>

On Wed, Mar 05, 2003 at 11:13:02PM +0100, Adrian Bunk wrote:
 > > Dave Jones <davej@codemonkey.org.uk>:
 > >   o [WATCHDOG] Merge AMD 766/768 TCO Timer/Watchdog driver from 2.4
 > amd7xx_tco.c contains the obsolete EXPORT_NO_SYMBOLS. The following 
 > patch corrects this bug:

Ack, that fix was already in my bk tree at
bk://linux-dj.bkbits.net/watchdog  I guess I forgot to
remind Linus to pull again after taking the first batch of changes.

Linus, pull again, and it should suck it in for next time.

		Dave


  reply	other threads:[~2003-03-05 22:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  3:48 Linux 2.5.64 Linus Torvalds
2003-03-05 14:36 ` Christoph Hellwig
2003-03-05 17:19   ` Dave Jones
2003-03-06  1:06     ` Alan Cox
2003-03-06  0:42       ` Dave Jones
2003-03-05 19:53 ` 2.5.64: cpufreq "userspace" governor doesn't compile Adrian Bunk
2003-03-06 17:28   ` Russell King
2003-03-06 17:16     ` Patrick Mochel
2003-03-06 23:31     ` [PATCH] cpufreq (2/7): fix userspace governor [Was: Re: 2.5.64: cpufreq "userspace" governor doesn't compile] Dominik Brodowski
2003-03-05 22:13 ` [2.5 patch] remove EXPORT_NO_SYMBOLS from amd7xx_tco Adrian Bunk
2003-03-05 23:57   ` Dave Jones [this message]
2003-03-05 23:49 ` Linux 2.5.64 John Cherry
2003-03-06 10:39 ` Geert Uytterhoeven

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=20030305235644.GA23028@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zwane@linuxpower.ca \
    /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