mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: sparc tree build warning
Date: Fri, 29 Jan 2010 10:25:43 +1100	[thread overview]
Message-ID: <20100129102543.7af32673.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100128.052432.251700168.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

Hi Dave,

On Thu, 28 Jan 2010 05:24:32 -0800 (PST) David Miller <davem@davemloft.net> wrote:
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu, 28 Jan 2010 18:44:23 +1100
> 
> > I am still seeing these.  Is it my compiler version (gcc4.4.0)?
> 
> You can't turn on DEBUG_STRICT_USER_COPY_CHECKS and
> expect a successful build.  It's for developers to
> look at the errors that are generated and audit those
> cases in detail.

These are defconfig builds and CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is
not set in either case.

> You'll get the same exact errors as on i386.

I only do an i386 defconfig build and I don't get these warnings.

> Please just elide the option from your test builds.

I would if I could :-)

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-01-28 23:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14  5:33 Stephen Rothwell
2009-12-14  7:01 ` David Miller
2009-12-14  8:55   ` Stephen Rothwell
2009-12-14  7:40 ` David Miller
2009-12-14  9:00   ` Stephen Rothwell
2010-01-28  7:44 ` Stephen Rothwell
2010-01-28 13:24   ` David Miller
2010-01-28 23:25     ` Stephen Rothwell [this message]
2010-01-29  4:12       ` David Miller
2010-01-29  6:32         ` Stephen Rothwell

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=20100129102543.7af32673.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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

all inboxes | Powered by JetHome®