From: Roland Dreier <rdreier@cisco.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: mshefty@ichips.intel.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH 1/7] AMSO1100 Makefiles and Kconfig changes.
Date: Wed, 31 May 2006 13:36:44 -0700 [thread overview]
Message-ID: <ada8xoix76r.fsf@cisco.com> (raw)
In-Reply-To: <20060531182735.3652.44197.stgit@stevo-desktop> (Steve Wise's message of "Wed, 31 May 2006 13:27:35 -0500")
Can you reorder things so these changes go last? Otherwise after this
patch we're left with a kernel tree that has a Makefile that refers to
sources that don't exist yet. It's not really a practical issue but
it is neater to do that way.
(It's easy to do in stgit -- just pop all the patches and then use
"stg push <name>" to push them in a different order)
- R.
next prev parent reply other threads:[~2006-05-31 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 18:27 [PATCH 0/7][RFC] Ammasso 1100 iWARP Driver Steve Wise
2006-05-31 18:27 ` [PATCH 1/7] AMSO1100 Makefiles and Kconfig changes Steve Wise
2006-05-31 20:36 ` Roland Dreier [this message]
2006-05-31 20:39 ` Steve Wise
2006-05-31 18:27 ` [PATCH 2/7] AMSO1100 Low Level Driver Steve Wise
2006-05-31 18:59 ` Stephen Hemminger
2006-06-07 15:56 ` Steve Wise
2006-05-31 18:27 ` [PATCH 3/7] AMSO1100 WR / Event Definitions Steve Wise
2006-05-31 18:27 ` [PATCH 4/7] AMSO1100 OpenFabrics Provider Steve Wise
2006-05-31 18:27 ` [PATCH 5/7] AMSO1100 Memory Management Steve Wise
2006-05-31 18:27 ` [PATCH 6/7] AMSO1100 Message Queues Steve Wise
2006-05-31 18:27 ` [PATCH 7/7] AMSO1100: Privileged Verbs Queues Steve Wise
2006-05-31 20:50 ` [PATCH 3/7] AMSO1100 WR / Event Definitions Steve Wise
2006-06-01 13:20 ` Steve Wise
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=ada8xoix76r.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mshefty@ichips.intel.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=swise@opengridcomputing.com \
/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.