All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hiremath, Vaibhav" <hvaibhav@ti.com>
To: "Hilman, Kevin" <khilman@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 0/5] OMAP3EVM: Board bug fixes/enhancements
Date: Fri, 28 Jan 2011 00:16:07 +0530	[thread overview]
Message-ID: <19F8576C6E063C45BE387C64729E739404BD7BE82E@dbde02.ent.ti.com> (raw)
In-Reply-To: <87pqrinq8x.fsf@ti.com>

> -----Original Message-----
> From: Hilman, Kevin
> Sent: Friday, January 28, 2011 12:12 AM
> To: Hiremath, Vaibhav
> Cc: linux-omap@vger.kernel.org; linux-arm-kernel@lists.infradead.org
> Subject: Re: [PATCH 0/5] OMAP3EVM: Board bug fixes/enhancements
> 
> Vaibhav Hiremath <hvaibhav@ti.com> writes:
> 
> > The current linux-omap/master is broken for lots of features/modules
> > and also there are few enhancements required with addition of AM/DM37x
> > family of devices.
> >
> > 	- Migrate TWL gpio_xxx api to gpio_xx_cansleep
> > 	- TSC: Driver init fails due to missing VIO regulator
> > 	- TSC: Wakeup is broken, enable the wakeup capability
> > 	- DSS: Addition of Mux changes for AM/DM37x
> > 	- Make Backlight gpio off in default state
> >
> > Note: Resetting the revision of patches since this is first bundled
> series.
> 
> Again, please state exactly what tree and commit this applies to, as it
> does not apply cleanly to l-o master.
> 
> Specifically,
> 
> > Vaibhav Hiremath (5):
> >   OMAP:board-omap3evm: Change TWL related gpio API's to gpio*_cansleep
> >   OMAP3EVM: Add vio regulator supply required for ads7846 TSC driver
> >   AM/DM37x: DSS mux configuration for >Rev-B processor cards
> 
> This one doesn't apply without fuzz.
> 
> >   OMAP3EVM: Made backlight GPIO default state to off
> >   OMAP3EVM: Set TSC wakeup option in pad config
> 
> And this one doesn't apply as it seems to apply on top of code that
> doesn't exist upstream.
> 
[Hiremath, Vaibhav] Kevin,

You should first apply Ethernet-reset patch first, and then all patches will get applied cleanly. I have tested it here at my end. 

Since you already acked Ethernet patch, I thought it will make its way to mainline before all these patches. And also while posting, I posted Ethernet patch again first and then this series.


Thanks,
Vaibhav

> Kevin


WARNING: multiple messages have this Message-ID (diff)
From: hvaibhav@ti.com (Hiremath, Vaibhav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] OMAP3EVM: Board bug fixes/enhancements
Date: Fri, 28 Jan 2011 00:16:07 +0530	[thread overview]
Message-ID: <19F8576C6E063C45BE387C64729E739404BD7BE82E@dbde02.ent.ti.com> (raw)
In-Reply-To: <87pqrinq8x.fsf@ti.com>

> -----Original Message-----
> From: Hilman, Kevin
> Sent: Friday, January 28, 2011 12:12 AM
> To: Hiremath, Vaibhav
> Cc: linux-omap at vger.kernel.org; linux-arm-kernel at lists.infradead.org
> Subject: Re: [PATCH 0/5] OMAP3EVM: Board bug fixes/enhancements
> 
> Vaibhav Hiremath <hvaibhav@ti.com> writes:
> 
> > The current linux-omap/master is broken for lots of features/modules
> > and also there are few enhancements required with addition of AM/DM37x
> > family of devices.
> >
> > 	- Migrate TWL gpio_xxx api to gpio_xx_cansleep
> > 	- TSC: Driver init fails due to missing VIO regulator
> > 	- TSC: Wakeup is broken, enable the wakeup capability
> > 	- DSS: Addition of Mux changes for AM/DM37x
> > 	- Make Backlight gpio off in default state
> >
> > Note: Resetting the revision of patches since this is first bundled
> series.
> 
> Again, please state exactly what tree and commit this applies to, as it
> does not apply cleanly to l-o master.
> 
> Specifically,
> 
> > Vaibhav Hiremath (5):
> >   OMAP:board-omap3evm: Change TWL related gpio API's to gpio*_cansleep
> >   OMAP3EVM: Add vio regulator supply required for ads7846 TSC driver
> >   AM/DM37x: DSS mux configuration for >Rev-B processor cards
> 
> This one doesn't apply without fuzz.
> 
> >   OMAP3EVM: Made backlight GPIO default state to off
> >   OMAP3EVM: Set TSC wakeup option in pad config
> 
> And this one doesn't apply as it seems to apply on top of code that
> doesn't exist upstream.
> 
[Hiremath, Vaibhav] Kevin,

You should first apply Ethernet-reset patch first, and then all patches will get applied cleanly. I have tested it here at my end. 

Since you already acked Ethernet patch, I thought it will make its way to mainline before all these patches. And also while posting, I posted Ethernet patch again first and then this series.


Thanks,
Vaibhav

> Kevin

  reply	other threads:[~2011-01-27 18:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 17:37 [PATCH 0/5] OMAP3EVM: Board bug fixes/enhancements Vaibhav Hiremath
2011-01-25 17:37 ` Vaibhav Hiremath
2011-01-25 17:37 ` [PATCH 1/5] OMAP:board-omap3evm: Change TWL related gpio API's to gpio*_cansleep Vaibhav Hiremath
2011-01-25 17:37   ` Vaibhav Hiremath
2011-01-28  7:56   ` Varadarajan, Charulatha
2011-01-28  7:56     ` Varadarajan, Charulatha
2011-01-25 17:37 ` [PATCH 2/5] OMAP3EVM: Add vio regulator supply required for ads7846 TSC driver Vaibhav Hiremath
2011-01-25 17:37   ` Vaibhav Hiremath
2011-01-25 17:37 ` [PATCH 3/5] AM/DM37x: DSS mux configuration for >Rev-B processor cards Vaibhav Hiremath
2011-01-25 17:37   ` Vaibhav Hiremath
2011-01-25 17:37 ` [PATCH 4/5] OMAP3EVM: Made backlight GPIO default state to off Vaibhav Hiremath
2011-01-25 17:37   ` Vaibhav Hiremath
2011-01-25 17:37 ` [PATCH 5/5] OMAP3EVM: Set TSC wakeup option in pad config Vaibhav Hiremath
2011-01-25 17:37   ` Vaibhav Hiremath
2011-01-27 18:42   ` Kevin Hilman
2011-01-27 18:42     ` Kevin Hilman
2011-02-17 22:19     ` Tony Lindgren
2011-02-17 22:19       ` Tony Lindgren
2011-02-22  6:01       ` Hiremath, Vaibhav
2011-02-22  6:01         ` Hiremath, Vaibhav
2011-01-27 18:41 ` [PATCH 0/5] OMAP3EVM: Board bug fixes/enhancements Kevin Hilman
2011-01-27 18:41   ` Kevin Hilman
2011-01-27 18:46   ` Hiremath, Vaibhav [this message]
2011-01-27 18:46     ` Hiremath, Vaibhav
2011-01-27 20:05     ` Kevin Hilman
2011-01-27 20:05       ` Kevin Hilman

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=19F8576C6E063C45BE387C64729E739404BD7BE82E@dbde02.ent.ti.com \
    --to=hvaibhav@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@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.