All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Andres Salomon <dilinger@queued.net>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	driverdevel <devel@driverdev.osuosl.org>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Jon Nettleton <jon.nettleton@gmail.com>
Subject: Re: linux-next: Tree for October 1 (staging/olpc_dcon)
Date: Sat, 2 Oct 2010 11:51:54 -0700	[thread overview]
Message-ID: <20101002185154.GA18020@suse.de> (raw)
In-Reply-To: <20101001192454.0a427cb0@debxo>

On Fri, Oct 01, 2010 at 07:24:54PM -0700, Andres Salomon wrote:
> On Fri, 1 Oct 2010 15:45:31 -0700
> Randy Dunlap <randy.dunlap@oracle.com> wrote:
> 
> > On Fri, 1 Oct 2010 15:37:56 +1000 Stephen Rothwell wrote:
> > 
> > > Hi all,
> > > 
> > > Changes since 20100930:
> > 
> > 
> > drivers/staging/olpc_dcon/olpc_dcon_xo_1.c:57: error: implicit
> > declaration of function 'geode_gpio_event_irq'
> > drivers/staging/olpc_dcon/olpc_dcon_xo_1.c:57: error: implicit
> > declaration of function 'geode_gpio'
> 
> Yep, it's pending a cs5535-gpio patch
> (https://patchwork.kernel.org/patch/209482/).

Wait, as I didn't apply the later patches, what I did apply should have
still built properly (remember our rule, no breakage at any point in a
patch series.)  So, should I revert the last olpc patch that caused this
problem?

thanks,

greg k-h

  reply	other threads:[~2010-10-02 18:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  5:37 linux-next: Tree for October 1 Stephen Rothwell
2010-10-01 22:41 ` linux-next: Tree for October 1 (staging/ft1000) Randy Dunlap
2010-10-04  8:29   ` Arnd Bergmann
2010-10-01 22:43 ` linux-next: Tree for October 1 (hwmon/pkgtemp) Randy Dunlap
2010-10-04 18:44   ` Fenghua Yu
2010-10-11 17:05     ` Randy Dunlap
2010-10-01 22:45 ` linux-next: Tree for October 1 (staging/olpc_dcon) Randy Dunlap
2010-10-02  2:24   ` Andres Salomon
2010-10-02 18:51     ` Greg KH [this message]
2010-10-03  1:03       ` Andres Salomon
2010-10-05 19:08         ` Greg KH
2010-10-05 19:33           ` Andres Salomon

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=20101002185154.GA18020@suse.de \
    --to=gregkh@suse.de \
    --cc=cjb@laptop.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dilinger@queued.net \
    --cc=jon.nettleton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.