All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: Question about recent copy_user.S change
Date: Sun, 01 Aug 2004 19:57:41 +0000	[thread overview]
Message-ID: <20040801195741.GY2334@holomorphy.com> (raw)
In-Reply-To: <20040801192158.GB7321@artsapartment.org>

On Sun, Aug 01, 2004 at 02:21:58PM -0500, Art Haas wrote:
> The 1.3->1.4 changes to the arch/sparc/lib/copy_user.S file added
> parenthesis to a number of macros within that file. The BK changlog
> associated with this change indicate the change was to make the
> file work with gcc-3.3.
> When looking at the changes made, I see that similar macros exist in
> memcpy.S as well, so would a patch adding parens to that file be
> worthwhile? Also, just what was the problem with gcc-3.3 that was
> resolved by adding the parenthesis? Macro mis-expansion I'm guessing.
> On a side note, the 2.6.8-rc2 kernel my SS20 has been using for the last
> several days has been, by far, the stablest 2.6 kernel run on that
> machine. I hate to write this for fear of jinxing things, but previous
> 2.6 kernels would boot and run for a while, and then the machine would
> get SCSI errors. Typically these errors occurred when doing something
> like 'cvs update', or compiling some software on the machine. The
> current kernel has had numerous cvs operations performed without
> problem, as well as several BitKeeper 'pull' operations and various
> builds without incident. Kudos to the kernel developers.

Could you post some system log information about the SCSI errors?

Thanks.


-- wli

  reply	other threads:[~2004-08-01 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 19:21 Question about recent copy_user.S change Art Haas
2004-08-01 19:57 ` William Lee Irwin III [this message]
2004-08-01 20:04 ` Art Haas
2004-08-02 17:00 ` Tom 'spot' Callaway
2004-08-02 18:09 ` Art Haas
2004-08-02 21:47 ` Question about recent copy_user.S change - with patch Art Haas
2004-08-02 21:51 ` William Lee Irwin III

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=20040801195741.GY2334@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=sparclinux@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 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.