From: Mark Maule <maule@sgi.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
akpm@osdl.org, j-nomura@ce.jp.nec.com
Subject: Re: [PATCH 2.6.16-rc6-mm1] fix ia64 MSI build problems
Date: Mon, 20 Mar 2006 14:13:13 -0600 [thread overview]
Message-ID: <20060320201313.GM31238@sgi.com> (raw)
In-Reply-To: <20060320195415.GA17263@suse.de>
On Mon, Mar 20, 2006 at 11:54:15AM -0800, Greg KH wrote:
> On Mon, Mar 20, 2006 at 01:36:38PM -0600, Mark Maule wrote:
> > Fix MSI-related build problems on ia64.
> >
> > Move arch/ia64/sn/pci/msi.c to drivers/pci/msi-altix.c
> > Move struct msi_ops in drivers/pci/msi.h to the top of the file so asm/msi.h
> > can make use of the declaration.
> > Clean up msi platform defintions in machvec.h (thanks to j-nomura@ce.jp.nec.com
> > for the patch to do that).
> >
> > Signed-off-by: Mark Maule <maule@sgi.com>
>
> Does this replace any of your pre-existing msi patches in my tree (and
> in -mm)? Shouldn't you just merge a few of them together now so that if
> someone were to apply stuff in order, the build is not broken for any
> step along the patch trail?
This patch just sits on top of the existing patchset.
>
> And also, the Makefile should be changed as Matthew pointed out.
>
> So, care to redo this?
Ok. I'll give it a bit of time for other potential comments to roll in
and then redo the original patchset.
Mark
prev parent reply other threads:[~2006-03-20 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 19:36 [PATCH 2.6.16-rc6-mm1] fix ia64 MSI build problems Mark Maule
2006-03-20 19:44 ` Matthew Wilcox
2006-03-20 19:54 ` Greg KH
2006-03-20 20:13 ` Mark Maule [this message]
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=20060320201313.GM31238@sgi.com \
--to=maule@sgi.com \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox