From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: adrian.bunk@movial.fi, chris@mips.com, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org
Subject: Re: mips: CONF_CM_DEFAULT build error
Date: Fri, 13 Jun 2008 14:55:38 +0100 [thread overview]
Message-ID: <20080613135538.GF703@linux-mips.org> (raw)
In-Reply-To: <20080602.012814.35471915.anemo@mba.ocn.ne.jp>
On Mon, Jun 02, 2008 at 01:28:14AM +0900, Atsushi Nemoto wrote:
> > Commit 351336929ccf222ae38ff0cb7a8dd5fd5c6236a0
> > ([MIPS] Allow setting of the cache attribute at run time.)
> > causes the following build error with pnx8550-jbs_defconfig
> > and pnx8550-stb810_defconfig:
>
> I wondered why the commit has my S-O-B, and finally found that I had
> fixed a section mismatch caused by the original patch (on queue tree
> on linux-mips.org) and Ralf had folded my fix into the original patch,
> with my S-O-B. Folding on the queue tree will be good on many case,
> but sometimes a bit confusing. :-)
Yes, I try to merge any follow on patches into the original patch as long
as that one is still sitting in the patch queue. Since that result in
bugs getting fixes before they ever show up in any of the more static
trees, that is the MIPS or kernel.org git trees there is little point in
documenting bugs "that never existed" and their "non-fixes" ;-)
Ralf
prev parent reply other threads:[~2008-06-13 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 17:07 mips: CONF_CM_DEFAULT build error Adrian Bunk
2008-06-01 16:28 ` Atsushi Nemoto
2008-06-13 13:55 ` Ralf Baechle [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=20080613135538.GF703@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=adrian.bunk@movial.fi \
--cc=anemo@mba.ocn.ne.jp \
--cc=chris@mips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.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