public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: Marc Dietrich <marvin24@gmx.de>,
	Mikael Pettersson <mikpe@it.uu.se>,
	"Olof Johansson (olof@lixom.net)" <olof@lixom.net>,
	"Greg KH (gregkh@suse.de)" <gregkh@suse.de>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Julian Andres Klode <jak@jak-linux.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	Leon Romanovsky <leon@leon.nu>,
	"Colin Cross (ccross@android.com)" <ccross@android.com>
Subject: Re: [PATCH] fix drivers/staging/nvec linkage error when keyboard is disabled
Date: Mon, 17 Oct 2011 15:20:55 -0700	[thread overview]
Message-ID: <20111017222055.GA2427@kroah.com> (raw)
In-Reply-To: <20111017222019.GA2410@kroah.com>

On Mon, Oct 17, 2011 at 03:20:19PM -0700, Greg KH wrote:
> On Mon, Oct 10, 2011 at 10:25:07AM -0700, Stephen Warren wrote:
> > Marc Dietrich wrote at Sunday, October 09, 2011 9:48 AM:
> > > Hi Mikael,
> > > 
> > > thanks for review. The nvec driver received some overhaul in the 3.1 release cycle
> > > and he fruids can be viewed in linux-next tree. The nvec client drivers were
> > > converted to mfd children in the mean time. This solves the build error, but is not
> > > very flexible. We are planing to move the mfd stuct to the board file(s) in the next
> > > cycle.
> > 
> > Indeed, the code in v3.1-rc9 is quite different to that in linux-next, so
> > this exact problem doesn't exist in linux-next.
> > 
> > However, don't we still want to solve build problems for the final v3.1
> > release, or a stable update to that? As such,
> > 
> > Acked-by: Stephen Warren <swarren@nvidia.com>
> > 
> > I also CC'd the staging maintainer Greg KH and Tegra maintainers Olof and
> > Colin on this email.
> 
> I'm confused, what patch should I apply here?  Can someone please resend
> it in a format that I can apply it in?  With the proper acks?

Nevermind, it already was, sorry for the noise...


      reply	other threads:[~2011-10-17 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 17:29 [PATCH] fix drivers/staging/nvec linkage error when keyboard is disabled Mikael Pettersson
2011-10-09 15:47 ` Marc Dietrich
2011-10-10 17:25   ` Stephen Warren
2011-10-10 20:20     ` Julian Andres Klode
2011-10-11  8:15       ` Re: [PATCH] fix drivers/staging/nvec linkage error when keyboard isdisabled Marc Dietrich
2011-10-12  9:19         ` Julian Andres Klode
2011-10-17 22:20     ` [PATCH] fix drivers/staging/nvec linkage error when keyboard is disabled Greg KH
2011-10-17 22:20       ` Greg KH [this message]

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=20111017222055.GA2427@kroah.com \
    --to=greg@kroah.com \
    --cc=ccross@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=jak@jak-linux.org \
    --cc=leon@leon.nu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marvin24@gmx.de \
    --cc=mikpe@it.uu.se \
    --cc=olof@lixom.net \
    --cc=swarren@nvidia.com \
    /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