public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>,
	Mikael Pettersson <mikpe-1zs4UD6AkMk@public.gmane.org>,
	"Olof Johansson (olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org)"
	<olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
	"Greg KH (gregkh-l3A5Bk7waGM@public.gmane.org)"
	<gregkh-l3A5Bk7waGM@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Julian Andres Klode <jak-4HMq4SXA452hPH1hqNUYSQ@public.gmane.org>,
	"devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org"
	<devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org>,
	Leon Romanovsky <leon-2ukJVAZIZ/Y@public.gmane.org>,
	"Colin Cross (ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org)"
	<ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] fix drivers/staging/nvec linkage error when keyboard is disabled
Date: Mon, 17 Oct 2011 15:20:19 -0700	[thread overview]
Message-ID: <20111017222019.GA2410@kroah.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173B23B539-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>

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-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> 
> 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?

thanks,

greg k-h

  parent reply	other threads:[~2011-10-17 22:20 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
     [not found] ` <20112.34922.209107.730268-tgku4HJDRZih8lFjZTKsyTAV6s6igYVG@public.gmane.org>
2011-10-09 15:47   ` Marc Dietrich
2011-10-10 17:25     ` Stephen Warren
     [not found]       ` <74CDBE0F657A3D45AFBB94109FB122FF173B23B539-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-10-10 20:20         ` Julian Andres Klode
     [not found]           ` <20111010202011.GA7220-4HMq4SXA452hPH1hqNUYSQ@public.gmane.org>
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         ` Greg KH [this message]
     [not found]           ` <20111017222019.GA2410-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2011-10-17 22:20             ` [PATCH] fix drivers/staging/nvec linkage error when keyboard is disabled Greg KH

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=20111017222019.GA2410@kroah.com \
    --to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
    --cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
    --cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org \
    --cc=gregkh-l3A5Bk7waGM@public.gmane.org \
    --cc=jak-4HMq4SXA452hPH1hqNUYSQ@public.gmane.org \
    --cc=leon-2ukJVAZIZ/Y@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marvin24-Mmb7MZpHnFY@public.gmane.org \
    --cc=mikpe-1zs4UD6AkMk@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    /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