From: Greg KH <greg@kroah.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: akpm@osdl.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 3/5] isicom: pci probing
Date: Tue, 13 Sep 2005 10:21:57 -0700 [thread overview]
Message-ID: <20050913172157.GC6309@kroah.com> (raw)
In-Reply-To: <200509131652.j8DGquXo022115@localhost.localdomain>
On Tue, Sep 13, 2005 at 06:52:56PM +0200, Jiri Slaby wrote:
> Signed-off-by: Jiri Slaby <xslaby@fi.muni.cz>
>
> drivers/char/isicom.c | 598 +++++++++++++++++++++++++++----------------------
> include/linux/isicom.h | 3
> 2 files changed, 333 insertions(+), 268 deletions(-)
>
> diff --git a/drivers/char/isicom.c b/drivers/char/isicom.c
> --- a/drivers/char/isicom.c
> +++ b/drivers/char/isicom.c
> @@ -91,6 +91,8 @@
> * 06/01/05 Alan Cox Merged the ISI and base kernel strands
> * into a single 2.6 driver
> *
> + * 10/09/05 Jiri Slaby driver rewritten to 2.6 API
> + *
The git changelog works well enough that you don't need to add stuff to
the files themselves anymore.
> +#define InterruptTheCard(base) outw(0, (base) + 0xc)
> +#define ClearInterrupt(base) inw((base) + 0x0a)
> +
> +#ifdef ISICOM_DEBUG
> +#define pr_deb(str, ...) printk((str), ##args);
> +#define isicom_paranoia_check(a, b, c) __isicom_paranoia_check((a), (b), (c))
> +#else
> +#define pr_deb(str, ...)
> +#define isicom_paranoia_check(a, b, c) 0
> +#endif
This doesn't look like "pci probe changes" In fact, a lot of other
changes in this patch don't look like them either...
Care to split it up even more?
thanks,
greg k-h
next prev parent reply other threads:[~2005-09-13 17:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 23:19 [PATCH -mm 1/2] drivers/char/isicom old api rewritten Jiri Slaby
2005-09-10 23:21 ` [PATCH -mm 2/2] drivers/char/isicom whitespace cleanup Jiri Slaby
2005-09-10 23:53 ` [PATCH -mm 1/2] drivers/char/isicom old api rewritten Andrew Morton
2005-09-11 22:04 ` [PATCH] drivers/char/isicom old api rewritten (round 2) Jiri Slaby
2005-09-11 22:20 ` Andrew Morton
2005-09-11 23:11 ` [PATCH] drivers/char/isicom old api rewritten (round 3) Jiri Slaby
2005-09-12 4:58 ` Greg KH
2005-09-12 12:58 ` [PATCH] drivers/char/isicom whitespace cleanup Jiri Slaby
2005-09-13 16:49 ` [PATCH 0/5] isicom char driver to 2.6 api Jiri Slaby
2005-09-13 16:52 ` [PATCH 3/5] isicom: pci probing Jiri Slaby
2005-09-13 17:21 ` Greg KH [this message]
2005-09-14 0:10 ` [PATCH 0/6] isicom char driver rewritten to 2.6 api Jiri Slaby
2005-09-14 0:12 ` [PATCH 1/6] isicom: Whitespace cleanup Jiri Slaby
2005-09-14 0:12 ` [PATCH 2/6] isicom: Type conversion and variables deletion Jiri Slaby
2005-09-14 0:12 ` [PATCH 3/6] isicom: Others little changes Jiri Slaby
2005-09-14 0:13 ` [PATCH 4/6] isicom: Pci probing added Jiri Slaby
2005-09-14 0:13 ` [PATCH 5/6] isicom: Firmware loading Jiri Slaby
2005-09-14 0:13 ` [PATCH 6/6] isicom: More whitespaces and coding style Jiri Slaby
2005-09-13 16:52 ` [PATCH 1/5] isicom: whitespace Jiri Slaby
2005-09-13 16:52 ` [PATCH 4/5] isicom: firmware Jiri Slaby
2005-09-13 16:52 ` [PATCH 2/5] isicom: types Jiri Slaby
2005-09-13 16:52 ` [PATCH 5/5] isicom: more whitespace Jiri Slaby
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=20050913172157.GC6309@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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