public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Kozlowski <mk@lab.zgora.pl>
To: Narendra_K@Dell.com
Cc: mk@lab.zgora.pl, sfr@canb.auug.org.au,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: linux-next: Tree for March 7
Date: Tue, 8 Mar 2011 21:57:32 +0100	[thread overview]
Message-ID: <20110308205732.GA17743@mako-laptop> (raw)
In-Reply-To: <20110307201215.GB22450@fedora14-r610.oslab.blr.amer.dell.com>

On Mon, Mar 07, 2011 at 11:52:04AM -0800, Narendra_K@Dell.com wrote:
> On Tue, Mar 08, 2011 at 12:35:37AM +0530, Mariusz Kozlowski wrote:
> > On Mon, Mar 07, 2011 at 06:05:47PM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > Changes since 20110304:
> > 
> > drivers/pci/pci-label.c: In function 'pci_create_firmware_label_files':
> > drivers/pci/pci-label.c:366: error: implicit declaration of function 'device_has_dsm'
> > 
> > Fails for !CONFIG_ACPI.
> > 
> > pci_create_firmware_label_files() uses device_has_dsm() which definition
> > is under #ifdef CONFIG_ACPI.
> > 
> 
> Hello,
> 
> Sorry for the inconvenience. I sent a fix for this just now.
> 
> http://marc.info/?l=linux-next&m=129952710415436&w=2

One more thing poped up today:

drivers/built-in.o: In function `dsm_label_utf16s_to_utf8s':
/home/linux/linux-2.6/drivers/pci/pci-label.c:193: undefined
reference to `utf16s_to_utf8s'

Linker fails when CONFIG_NLS != y.

-- 
Mariusz Kozlowski

  reply	other threads:[~2011-03-08 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07  7:05 linux-next: Tree for March 7 Stephen Rothwell
2011-03-07 19:05 ` Mariusz Kozlowski
2011-03-07 19:52   ` Narendra_K
2011-03-08 20:57     ` Mariusz Kozlowski [this message]
2011-03-09 16:45       ` Mariusz Kozlowski
2011-03-07 19:34 ` [PATCH] staging/hv: add missing include causing build error Mariusz Kozlowski

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=20110308205732.GA17743@mako-laptop \
    --to=mk@lab.zgora.pl \
    --cc=Narendra_K@Dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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