All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: devel@driverdev.osuosl.org, b-cousson@ti.com, j-keerthy@ti.com,
	linux-kernel@vger.kernel.org, kbaidarov@dev.rtsoft.ru,
	grant.likely@secretlab.ca
Subject: Re: [PATCHv4 0/4] staging: adding OMAP bandgap driver
Date: Mon, 16 Jul 2012 19:05:19 -0700	[thread overview]
Message-ID: <20120717020519.GA20277@kroah.com> (raw)
In-Reply-To: <1342108952-12987-1-git-send-email-eduardo.valentin@ti.com>

On Thu, Jul 12, 2012 at 07:02:28PM +0300, Eduardo Valentin wrote:
> Greg,
> 
> Here is again the OMAP BG driver, under staging area.
> I fixed the compilation issue I didn't see, wrt implicit function
> declarations. As I mentioned on other thread, my compilation test
> didn't see it, that's why I thought it was fine to send it.
> 
> I also limited the driver compilation to OMAP4/5.

I edited the Makefile part of the patch by hand, and applied these
patches, can you pull my tree and verify that I didn't break anything?

thanks,

greg k-h

  parent reply	other threads:[~2012-07-17  2:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 16:02 [PATCHv4 0/4] staging: adding OMAP bandgap driver Eduardo Valentin
2012-07-12 16:02 ` [PATCHv4 1/4] staging: OMAP4+: thermal: introduce bandgap temperature sensor Eduardo Valentin
2012-07-17  2:02   ` Greg Kroah-Hartman
2012-07-12 16:02 ` [PATCHv4 2/4] staging: omap-thermal: common code to expose driver to thermal framework Eduardo Valentin
2012-07-12 16:02 ` [PATCHv4 3/4] staging: omap-thermal: add OMAP4 data structures Eduardo Valentin
2012-07-12 16:02 ` [PATCHv4 4/4] staging: omap-thermal: add OMAP5 " Eduardo Valentin
2012-07-17  2:05 ` Greg Kroah-Hartman [this message]
2012-07-18 16:24   ` [PATCHv4 0/4] staging: adding OMAP bandgap driver Valentin, Eduardo

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=20120717020519.GA20277@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=b-cousson@ti.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=eduardo.valentin@ti.com \
    --cc=grant.likely@secretlab.ca \
    --cc=j-keerthy@ti.com \
    --cc=kbaidarov@dev.rtsoft.ru \
    --cc=linux-kernel@vger.kernel.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 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.