From: Greg KH <gregkh@suse.de>
To: Zimny Lech <napohybelskurwysynom2010@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 9
Date: Thu, 9 Dec 2010 07:49:00 -0800 [thread overview]
Message-ID: <20101209154900.GA20190@suse.de> (raw)
In-Reply-To: <AANLkTikjGhkYoR_o3uq-sUEY1daXSRWQgRmMBoVJ-n1=@mail.gmail.com>
On Thu, Dec 09, 2010 at 12:46:19PM +0100, Zimny Lech wrote:
> Ave
>
> 2010/12/9 Stephen Rothwell <sfr@canb.auug.org.au>:
> > Hi all,
> >
> > Changes since 20101208:
> >
>
> LD drivers/built-in.o
> drivers/staging/built-in.o:(.data+0xec80): multiple definition of `log_level'
That's coming from the cxt1e1 driver, I'll fix that up to be a "sane"
global name.
> drivers/scsi/built-in.o:(.data+0xa71c): first defined here
That's coming from the drivers/scsi/bfa/ driver, and it too should be
fixed as it shouldn't have a global variable with this name in it. Care
to let the maintainer of that driver know about this as well?
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-09 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 4:41 linux-next: Tree for December 9 Stephen Rothwell
2010-12-09 11:46 ` Zimny Lech
2010-12-09 15:49 ` Greg KH [this message]
2010-12-09 16:42 ` Zimny Lech
2010-12-09 19:35 ` Jing Huang
2010-12-09 17:38 ` [PATCH -next] staging: solo6010 depends on I2C Randy Dunlap
2010-12-09 20:29 ` linux-next: Tree for December 9 Zimny Lech
-- strict thread matches above, loose matches on Subject: below --
2009-12-09 6:47 Stephen Rothwell
2008-12-09 7:52 Stephen Rothwell
2008-12-09 8:53 ` Al Viro
2008-12-09 23:34 ` Andrew Morton
2008-12-10 0:06 ` Kay Sievers
2008-12-10 0:15 ` Andrew Morton
2008-12-10 0:31 ` Kay Sievers
2008-12-10 1:30 ` Andrew Morton
2008-12-10 1:36 ` Kay Sievers
2008-12-10 1:42 ` NeilBrown
2008-12-10 1:58 ` Andrew Morton
2008-12-10 19:16 ` Andrew Morton
2008-12-10 22:15 ` Neil Brown
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=20101209154900.GA20190@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).