mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Daniel Walker <dwalker@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] drivers: staging: dream: fix smd in makefile
Date: Fri, 7 May 2010 09:56:53 -0700	[thread overview]
Message-ID: <20100507165653.GB795@kroah.com> (raw)
In-Reply-To: <1273190401.20494.44.camel@c-dwalke-linux.qualcomm.com>

On Thu, May 06, 2010 at 05:00:01PM -0700, Daniel Walker wrote:
> On Thu, 2010-05-06 at 16:54 -0700, Greg KH wrote:
> > On Thu, May 06, 2010 at 04:48:59PM -0700, Daniel Walker wrote:
> > > Not sure about this one.. Cause if you apply this then some SMD files
> > > don't compile anymore. There's some missing config options related to
> > > AMSS.
> > > 
> > > NOT-Signed-off-by: Daniel Walker <dwalker@codeaurora.org>
> > 
> > Heh, I'm not going to apply this then :)
> > 
> > > CC: Greg KH <greg@kroah.com>
> > > Cc: Pavel Machek <pavel@ucw.cz>
> > > ---
> > >  drivers/staging/dream/Makefile |    3 ++-
> > 
> > With the recent progression of your arch tree, and the
> > wakelock/suspend-blocker stuff, what's the need for these files to still
> > be in the staging directory at all?  Can't it be deleted and it go
> > through your tree?
> 
> Yeah, all the smd stuff can .. The rest of it should stay for now I
> think. I'm not ready to take on those other specific drivers, like the
> camera etc..
> 
> Should I just send a patch to drop the whole SMD directory then?

Yes, I think so.  Pavel, any objections?

thanks,

greg k-h

      reply	other threads:[~2010-05-07 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 23:48 Daniel Walker
2010-05-06 23:54 ` Greg KH
2010-05-07  0:00   ` Daniel Walker
2010-05-07 16:56     ` 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=20100507165653.GB795@kroah.com \
    --to=greg@kroah.com \
    --cc=dwalker@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®