All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Hanna Linder <hannal@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@lists.osdl.org,
	greg@kroah.com
Subject: [Kernel-janitors] Re: [PATCH 2.6] pci-hplj.c: replace
Date: Mon, 04 Oct 2004 21:41:07 +0000	[thread overview]
Message-ID: <20041004214107.GA2160@linux-mips.org> (raw)
In-Reply-To: <281940000.1096925207@w-hlinder.beaverton.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

On Mon, Oct 04, 2004 at 02:26:47PM -0700, Hanna Linder wrote:

> As pci_find_device is going away I have replaced this call with pci_get_device.

Looks good ...

> If  someone has access to an RM200 or RM300 and could test this I would appreciate it.

Except that piece of code isn't for an RM[23]00 but a HP Laserjet (yes,
that paper eating thing ;-) and hasn't seen any update or feedback from
the original submitters since the original submission, so the entire HPLJ
code is a candidate for removal ...

   Ralf

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@linux-mips.org>
To: Hanna Linder <hannal@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@lists.osdl.org,
	greg@kroah.com
Subject: Re: [PATCH 2.6] pci-hplj.c: replace pci_find_device with pci_get_device
Date: Mon, 4 Oct 2004 23:41:07 +0200	[thread overview]
Message-ID: <20041004214107.GA2160@linux-mips.org> (raw)
In-Reply-To: <281940000.1096925207@w-hlinder.beaverton.ibm.com>

On Mon, Oct 04, 2004 at 02:26:47PM -0700, Hanna Linder wrote:

> As pci_find_device is going away I have replaced this call with pci_get_device.

Looks good ...

> If  someone has access to an RM200 or RM300 and could test this I would appreciate it.

Except that piece of code isn't for an RM[23]00 but a HP Laserjet (yes,
that paper eating thing ;-) and hasn't seen any update or feedback from
the original submitters since the original submission, so the entire HPLJ
code is a candidate for removal ...

   Ralf

  reply	other threads:[~2004-10-04 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 21:26 [Kernel-janitors] [PATCH 2.6] pci-hplj.c: replace pci_find_device Hanna Linder
2004-10-04 21:26 ` [PATCH 2.6] pci-hplj.c: replace pci_find_device with pci_get_device Hanna Linder
2004-10-04 21:41 ` Ralf Baechle [this message]
2004-10-04 21:41   ` Ralf Baechle
2004-10-04 21:48   ` [Kernel-janitors] Re: [PATCH 2.6] pci-hplj.c: replace Hanna Linder
2004-10-04 21:48     ` [PATCH 2.6] pci-hplj.c: replace pci_find_device with pci_get_device Hanna Linder
2004-10-05 13:03   ` [Kernel-janitors] Re: [PATCH 2.6] pci-hplj.c: replace David Woodhouse
2004-10-05 13:03     ` [PATCH 2.6] pci-hplj.c: replace pci_find_device with pci_get_device David Woodhouse
2004-10-05 13:36     ` [Kernel-janitors] Re: [PATCH 2.6] pci-hplj.c: replace Ralf Baechle
2004-10-05 13:36       ` [PATCH 2.6] pci-hplj.c: replace pci_find_device with pci_get_device Ralf Baechle

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=20041004214107.GA2160@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=greg@kroah.com \
    --cc=hannal@us.ibm.com \
    --cc=kernel-janitors@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.