From: Roland Dreier <rdreier@cisco.com>
To: Heiko Joerg Schick <info@schihei.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [openib-general] Re: [PATCH 00/16] ehca: IBM eHCA InfiniBand Device Driver
Date: Mon, 01 May 2006 10:03:24 -0700 [thread overview]
Message-ID: <ada8xply8wz.fsf@cisco.com> (raw)
In-Reply-To: <e2r7a0$fo2$1@sea.gmane.org> (Heiko Joerg Schick's message of "Thu, 27 Apr 2006 21:50:28 +0200")
Heiko> I don't like the idea to put the whole driver in one patch
Heiko> file. I would propose to put the patch "ehca: integration
Heiko> in Linux kernel" last instead of first, as Arnd
Heiko> mentioned. With that change we leave the kernel in a
Heiko> working state when applying the patches.
Yes, that makes sense.
And I can fold the patches into a single git changeset when we finally
merge it, since I don't see any advantage to having the driver split
into pieces. (No one is going to git biset a half-applied driver or
anything like that)
- R.
WARNING: multiple messages have this Message-ID (diff)
From: Roland Dreier <rdreier@cisco.com>
To: Heiko Joerg Schick <info@schihei.de>
Cc: openib-general@openib.org, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [openib-general] Re: [PATCH 00/16] ehca: IBM eHCA InfiniBand Device Driver
Date: Mon, 01 May 2006 10:03:24 -0700 [thread overview]
Message-ID: <ada8xply8wz.fsf@cisco.com> (raw)
In-Reply-To: <e2r7a0$fo2$1@sea.gmane.org> (Heiko Joerg Schick's message of "Thu, 27 Apr 2006 21:50:28 +0200")
Heiko> I don't like the idea to put the whole driver in one patch
Heiko> file. I would propose to put the patch "ehca: integration
Heiko> in Linux kernel" last instead of first, as Arnd
Heiko> mentioned. With that change we leave the kernel in a
Heiko> working state when applying the patches.
Yes, that makes sense.
And I can fold the patches into a single git changeset when we finally
merge it, since I don't see any advantage to having the driver split
into pieces. (No one is going to git biset a half-applied driver or
anything like that)
- R.
next prev parent reply other threads:[~2006-05-01 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 12:05 [PATCH 00/16] ehca: IBM eHCA InfiniBand Device Driver Heiko J Schick
2006-04-27 12:57 ` Jörn Engel
2006-04-27 12:57 ` Jörn Engel
2006-04-27 19:50 ` Heiko Joerg Schick
2006-04-27 19:50 ` Heiko Joerg Schick
2006-05-01 17:03 ` Roland Dreier [this message]
2006-05-01 17:03 ` [openib-general] " Roland Dreier
2006-05-03 12:43 ` Andrew Morton
2006-05-03 12:43 ` Andrew Morton
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=ada8xply8wz.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=info@schihei.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=openib-general@openib.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.