From: John Cherry <cherry@osdl.org>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: akpm@osdl.org, linux-mm@kvack.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] aic7xxx parallel build
Date: Thu, 22 Jan 2004 16:54:32 -0800 [thread overview]
Message-ID: <1074819272.15610.2.camel@cherrypit.pdx.osdl.net> (raw)
In-Reply-To: <1251588112.1074819190@aslan.btc.adaptec.com>
Yeah. It looks like I grabbed my old patch from the last successful
parallel build that Andrew ran.
I'll run the regressions on the Makefiles you have supplied tonight. I
have no doubts that this will be successful. Thanks.
John
On Thu, 2004-01-22 at 16:53, Justin T. Gibbs wrote:
> > The Makefiles for aic7xxx and aicasm have changed since I submitted a
> > patch for the parallel build problem several months ago. Justin's patch
> > has disappeared from the mm builds, so we continue to have parallel
> > build problems.
> >
> > The following patch fixes the parallel build problem and it still
> > applies to 2.6.2-rc1-mm1. This is Justin's fix.
>
> Actually, that's not my fix. This looks like your original fix.
> I've attached aic7xxx/Makefile and aic7xxx/aicasm/Makefile from my
> tree. These seem to work just fine in my parallel build tests and
> will work regardless of which generated file is out of date - a flaw
> in your change. Please let me know if these files don't work for you.
>
> --
> Justin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-01-23 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 19:38 John Cherry
2004-01-23 0:53 ` Justin T. Gibbs
2004-01-23 0:54 ` John Cherry [this message]
2004-01-23 1:05 ` John Cherry
[not found] ` <20040122174458.0bdf5f26.akpm@osdl.org>
2004-01-23 19:48 ` John Cherry
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=1074819272.15610.2.camel@cherrypit.pdx.osdl.net \
--to=cherry@osdl.org \
--cc=akpm@osdl.org \
--cc=gibbs@scsiguy.com \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@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