public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@xenotime.net>
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 Jun 27 (eliminated_printk)
Date: Wed, 27 Jun 2012 09:29:29 -0700	[thread overview]
Message-ID: <1340814569.16533.53.camel@joe2Laptop> (raw)
In-Reply-To: <4FEB340D.3040908@xenotime.net>

On Wed, 2012-06-27 at 09:25 -0700, Randy Dunlap wrote:
> On 06/26/2012 08:22 PM, Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > This tree was not built between each merge, but only after merging all
> > the trees.
> > 
> > Changes since 20120626:
> 
> 
> 
> on i386:
> 
> drivers/platform/x86/thinkpad_acpi.c: In function 'drv_acpi_handle_init':
> drivers/platform/x86/thinkpad_acpi.c:684:2: error: implicit declaration of function 'eliminated_printk'
> 
> drivers/platform/x86/fujitsu-laptop.c: In function 'call_fext_func':
> drivers/platform/x86/fujitsu-laptop.c:223:3: error: implicit declaration of function 'eliminated_printk'
> 
> 
> Full randconfig file is attached.

Thanks Randy.

This patch depends on the first patch in the series
which hasn't been applied.

https://lkml.org/lkml/2012/6/17/229
https://lkml.org/lkml/2012/6/17/231



  reply	other threads:[~2012-06-27 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  3:22 linux-next: Tree for Jun 27 Stephen Rothwell
2012-06-27 16:09 ` linux-next: Tree for Jun 27 (vfio) Randy Dunlap
2012-06-27 19:20   ` Alex Williamson
2012-06-27 16:13 ` linux-next: Tree for Jun 27 (dm-thin.c) Randy Dunlap
2012-06-27 16:18   ` Alasdair G Kergon
2012-06-27 16:25 ` linux-next: Tree for Jun 27 (eliminated_printk) Randy Dunlap
2012-06-27 16:29   ` Joe Perches [this message]
2012-06-27 22:52     ` Stephen Rothwell
2012-06-28 20:14       ` Shuah Khan
2012-06-28 20:16         ` Matthew Garrett
2012-06-28 21:03           ` Shuah Khan

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=1340814569.16533.53.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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