From: Andrew Morton <akpm@osdl.org>
To: Markus Lidel <Markus.Lidel@shadowconnect.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2o_core.c, i2o_scsi.c minor bugfixes
Date: Mon, 19 Jan 2004 20:07:47 -0800 [thread overview]
Message-ID: <20040119200747.6e8d63d0.akpm@osdl.org> (raw)
In-Reply-To: <400BF755.6070201@shadowconnect.com>
Markus Lidel <Markus.Lidel@shadowconnect.com> wrote:
>
> Hello,
>
> after using the i2o modules (i2o_core and i2o_scsi), i found that there seems to be some minor problems in the 2.6.1 kernel
> version. So i have created a patch, which resolves the following issues:
>
>
> i2o-cleanup.patch:
I get 100% rejects applying this. Could you resend it as an attachment?
> --- drivers/message/i2o.old/i2o_core.c 2004-01-17 22:47:00.000000000 +0100
> +++ drivers/message/i2o/i2o_core.c 2004-01-17 23:34:43.866973586 +0100
Also, this renaming arrangement breaks my scripts (at least). Preferable
would be:
--- a/drivers/message/i2o/i2o_core.c
+++ b/drivers/message/i2o/i2o_core.c
> Also i found that the resource management in i2o_scsi is static, so i tried
> to make things a little bit dynamic by allocating the mapping tables at
> module insertion (not included in this e-mail). Because i don't saw a
> maintainer for those module, i wrote to the kernel mailing list. Can
> anybody tell me, who i can contact to verify if my changes are of any
> value? I want to contribute some more code, because on my system the
> i2o_block doesn't work too. But before, i want to be sure that my code is
> needed and also is good enough to be included into the kernel.
I think that would be Alan Cox <alan@lxorguk.ukuu.org.uk>
next prev parent reply other threads:[~2004-01-20 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 15:27 [PATCH] i2o_core.c, i2o_scsi.c minor bugfixes Markus Lidel
2004-01-20 4:07 ` Andrew Morton [this message]
2004-01-20 8:41 ` Markus Lidel
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=20040119200747.6e8d63d0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Markus.Lidel@shadowconnect.com \
--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