public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] remove bouncing email address of Thomas Hood
Date: Sun, 23 Jan 2005 11:17:28 +0100	[thread overview]
Message-ID: <20050123101728.GK3212@stusta.de> (raw)

This patch removes the bouncing email address of Thomas Hood (I haven't 
found any more recent email address).

Signed-off-by: Adrian Bunk <bunk@stusta.de>

---

 arch/i386/kernel/apm.c     |    4 ++--
 drivers/pnp/pnpbios/core.c |    2 +-
 drivers/pnp/pnpbios/proc.c |    2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

This patch was already sent on:
- 28 Nov 2004

--- linux-2.6.10-rc2-mm3-full/drivers/pnp/pnpbios/core.c.old	2004-11-28 23:33:19.000000000 +0100
+++ linux-2.6.10-rc2-mm3-full/drivers/pnp/pnpbios/core.c	2004-11-28 23:33:29.000000000 +0100
@@ -12,7 +12,7 @@
  * Minor reorganizations by David Hinds <dahinds@users.sourceforge.net>
  * Further modifications (C) 2001, 2002 by:
  *   Alan Cox <alan@redhat.com>
- *   Thomas Hood <jdthood@mail.com>
+ *   Thomas Hood
  *   Brian Gerst <bgerst@didntduck.org>
  *
  * Ported to the PnP Layer and several additional improvements (C) 2002
--- linux-2.6.10-rc2-mm3-full/drivers/pnp/pnpbios/proc.c.old	2004-11-28 23:33:38.000000000 +0100
+++ linux-2.6.10-rc2-mm3-full/drivers/pnp/pnpbios/proc.c	2004-11-28 23:33:44.000000000 +0100
@@ -2,7 +2,7 @@
  * /proc/bus/pnp interface for Plug and Play devices
  *
  * Written by David Hinds, dahinds@users.sourceforge.net
- * Modified by Thomas Hood, jdthood@mail.com
+ * Modified by Thomas Hood
  *
  * The .../devices and .../<node> and .../boot/<node> files are
  * utilized by the lspnp and setpnp utilities, supplied with the
--- linux-2.6.10-rc2-mm3-full/arch/i386/kernel/apm.c.old	2004-11-28 23:33:52.000000000 +0100
+++ linux-2.6.10-rc2-mm3-full/arch/i386/kernel/apm.c	2004-11-28 23:34:07.000000000 +0100
@@ -166,14 +166,14 @@
  *         If an APM idle fails log it and idle sensibly
  *   1.15: Don't queue events to clients who open the device O_WRONLY.
  *         Don't expect replies from clients who open the device O_RDONLY.
- *         (Idea from Thomas Hood <jdthood@mail.com>)
+ *         (Idea from Thomas Hood)
  *         Minor waitqueue cleanups. (John Fremlin <chief@bandits.org>)
  *   1.16: Fix idle calling. (Andreas Steinmetz <ast@domdv.de> et al.)
  *         Notify listeners of standby or suspend events before notifying
  *         drivers. Return EBUSY to ioctl() if suspend is rejected.
  *         (Russell King <rmk@arm.linux.org.uk> and Thomas Hood)
  *         Ignore first resume after we generate our own resume event
- *         after a suspend (Thomas Hood <jdthood@mail.com>)
+ *         after a suspend (Thomas Hood)
  *         Daemonize now gets rid of our controlling terminal (sfr).
  *         CONFIG_APM_CPU_IDLE now just affects the default value of
  *         idle_threshold (sfr).


             reply	other threads:[~2005-01-23 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 10:17 Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-28 22:39 [2.6 patch] remove bouncing email address of Thomas Hood Adrian Bunk

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=20050123101728.GK3212@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.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