public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v3.15-rc1
Date: Tue, 15 Apr 2014 14:18:34 +0200	[thread overview]
Message-ID: <1397564314.2056.10.camel@x41> (raw)
In-Reply-To: <1397561816-9289-1-git-send-email-geert@linux-m68k.org>

Geert Uytterhoeven schreef op di 15-04-2014 om 13:36 [+0200]:
>   + /scratch/kisskb/src/arch/x86/crypto/sha1_ssse3_glue.c: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]:  => 50:1
>   + /scratch/kisskb/src/arch/x86/crypto/sha256_ssse3_glue.c: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]:  => 56:1
>   + /scratch/kisskb/src/arch/x86/crypto/sha512_ssse3_glue.c: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]:  => 55:1
>   + /scratch/kisskb/src/arch/x86/kernel/machine_kexec_32.c: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]:  => 191:12
>   + /scratch/kisskb/src/arch/x86/kernel/syscall_32.c: warning: 'externally_visible' attribute ignored [-Wattributes]:  => 14:1

Probably all fixed with " [PATCH 1/3] Revert "lto: Make asmlinkage
__visible", see https://lkml.org/lkml/2014/4/1/757. (At least, similar
warnings were gone here with that patch applied.) Not sure were that
patch is queued.

>   + /scratch/kisskb/src/drivers/gpu/drm/i915/i915_cmd_parser.c: warning: format '%td' expects argument of type 'ptrdiff_t', but argument 5 has type 'long unsigned int' [-Wformat]:  => 405:4

Fixed by "[PATCH] Revert "drm/i915: fix build warning on 32-bit (v2)"",
see https://lkml.org/lkml/2014/4/7/119 . Is that one queued somewhere?

>   + /scratch/kisskb/src/drivers/scsi/hpsa.c: warning: 'trans_support' may be used uninitialized in this function [-Wuninitialized]:  => 7467:20

First reported (for linux-next it seems) in
https://lkml.org/lkml/2014/3/26/30 . Fix is currently discussed in the
(short) thread starting at https://lkml.org/lkml/2014/4/10/633 .


Paul Bolle


  parent reply	other threads:[~2014-04-15 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 11:36 Build regressions/improvements in v3.15-rc1 Geert Uytterhoeven
2014-04-15 11:44 ` Geert Uytterhoeven
2014-04-15 12:18 ` Paul Bolle [this message]
2014-04-15 13:53 ` Guenter Roeck

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=1397564314.2056.10.camel@x41 \
    --to=pebolle@tiscali.nl \
    --cc=geert@linux-m68k.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