From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: kbuild tree build warning
Date: Mon, 15 Jun 2009 09:06:55 +1000 [thread overview]
Message-ID: <20090615090655.9157bcc1.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090610064723.GA25493@uranus.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Hi Sam,
On Wed, 10 Jun 2009 08:47:23 +0200 Sam Ravnborg <sam@ravnborg.org> wrote:
>
> On Wed, Jun 10, 2009 at 11:52:55AM +1000, Stephen Rothwell wrote:
> >
> > Today's linux-next build (x86_64 allmodconfig) produced this warning:
> >
> > In file included from arch/x86/kernel/vmlinux.lds.S:23:
> > include/asm-generic/vmlinux.lds.h:726:47: warning: backslash-newline at end of file
> >
> > Caused by commit ef53dae8658cf0e93d380983824a661067948d87 ("Improve
> > vmlinux.lds.h support for arch specific linker scripts").
>
> I already fixed this locally but I forgot to do a "git commit --amend" :-)
> Will be fixed in next push of kbuild-next.
Then why didn't it make it into the version that just got into Linus'
tree? Also the other I mentioned:
include/asm-generic/vmlinux.lds.h:695:1: warning: "/*" within comment
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-14 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 1:52 Stephen Rothwell
2009-06-10 6:47 ` Sam Ravnborg
2009-06-10 6:55 ` Stephen Rothwell
2009-06-10 9:22 ` Stephen Rothwell
2009-06-14 23:06 ` Stephen Rothwell [this message]
2009-06-14 23:08 ` 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=20090615090655.9157bcc1.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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®