From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM: OMAP3: cm-t35: add regulator supply for ads7846
Date: Fri, 18 Nov 2011 16:14:28 -0800 [thread overview]
Message-ID: <20111119001428.GW31337@atomide.com> (raw)
In-Reply-To: <4EB92CE6.1000408@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [111108 04:47]:
> On 11/07/11 22:31, Tony Lindgren wrote:
> > * Igor Grinberg <grinberg@compulab.co.il> [111106 04:45]:
> >> Hi Tony,
> >>
> >> On 11/05/11 01:57, Tony Lindgren wrote:
> >>> * Tony Lindgren <tony@atomide.com> [111104 16:05]:
> >>>> * Igor Grinberg <grinberg@compulab.co.il> [111019 02:05]:
> >>>>
> >>>> Applying to board branch for v3.3 merge window.
> >>>
> >>> Hmm, actually I suggest you respin patches 2 and 3 so they apply
> >>> on their own to current fixes branch. Then update 1 and 4 to
> >>> apply on top of those.
> >>>
> >>> This way we can apply 2 and 3 during the -rc cycle, and then
> >>> queue 1 and 4 for the next merge window.
> >>
> >> Well, actually all them are fixes, although it cannot be understood
> >> from the subject.
> >> I will adjust the subjects (and may be the commit messages also)
> >> to be more specific and resend.
> >
> > Hmm 1 & 4 are "features that never worked" type fixes, so they
> > have flame potential. Those have to wait for the next merge window.
>
> Not exactly:
>
> 1/4 is a fix that I should have submitted more than a year ago,
> just after the ads7846 got support for the regulators:
Sounds like it's not that urgent then :)
> > Or I can just apply all of them into board branch to wait for the
> > next merge window.
>
> That can be an option, if it bothers you too much,
> but I prefer to have this already in 3.2.
I'll just apply them into board branch to wait for the next merge
window then.
Thanks,
Tony
next prev parent reply other threads:[~2011-11-19 0:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 9:39 [PATCH 0/4] ARM: OMAP3: cm-t35/cm-t3730 fixes Igor Grinberg
2011-10-19 9:39 ` [PATCH 1/4] ARM: OMAP3: cm-t35: add regulator supply for ads7846 Igor Grinberg
2011-11-04 23:39 ` Tony Lindgren
2011-11-04 23:57 ` Tony Lindgren
2011-11-06 13:19 ` Igor Grinberg
2011-11-07 20:31 ` Tony Lindgren
2011-11-08 13:21 ` Igor Grinberg
2011-11-19 0:14 ` Tony Lindgren [this message]
2011-11-20 8:38 ` Igor Grinberg
2011-10-19 9:39 ` [PATCH 2/4] ARM: OMAP3: cm-t35: fix DSS regulator supply Igor Grinberg
2011-10-19 9:39 ` [PATCH 3/4] ARM: OMAP3: cm-t35: fix audio Igor Grinberg
2011-10-19 11:03 ` Sergei Shtylyov
2011-10-19 13:56 ` Igor Grinberg
2011-10-19 14:01 ` [PATCH 3/4 v2] " Igor Grinberg
2011-10-19 9:39 ` [PATCH 4/4] arm: omap3: cm-t35: add reset for sb-t35 usb hub Igor Grinberg
2011-10-19 9:56 ` [PATCH 4/4 v2] ARM: OMAP3: " Igor Grinberg
2011-11-06 14:13 ` [PATCH v2 0/4] ARM: OMAP3: cm-t35/cm-t3730 fixes Igor Grinberg
2011-11-06 14:16 ` [PATCH v2 1/4] ARM: OMAP3: cm-t35: fix ads7846 touchscreen Igor Grinberg
2011-11-06 14:16 ` [PATCH v2 2/4] ARM: OMAP3: cm-t35: fix DSS regulator supply Igor Grinberg
2011-11-06 14:16 ` [PATCH v2 3/4] ARM: OMAP3: cm-t35: fix audio Igor Grinberg
2011-11-06 14:16 ` [PATCH v2 4/4] ARM: OMAP3: cm-t35: fix USB hub Igor Grinberg
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=20111119001428.GW31337@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).