From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap2+: hwmod: fix breakage introduced by d6504acd
Date: Mon, 7 Nov 2011 15:27:13 -0800 [thread overview]
Message-ID: <20111107232713.GD31337@atomide.com> (raw)
In-Reply-To: <20111107231632.GL15294@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [111107 14:41]:
> On Mon, Nov 07, 2011 at 03:07:28PM -0800, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [111107 14:20]:
> > > On Mon, Nov 07, 2011 at 02:51:57PM -0800, Tony Lindgren wrote:
> > > > Here's what I got. Looks like the removal of the sr[12]_hwmod
> > > > part is no longer needed, so only the r value check part is needed.
> > >
> > > Err. So do you have anything in your git tree which you're pushing out
> > > this evening which removes the sr[12]_hwmod from the omap_3xxx_hwmod
> > > list?
> > >
> > > If not, how does that bug get fixed in mainline?
> >
> > Ah sorry, there's also the following commit there that deals
> > with other related issues:
>
> Great, so it looks like everything that I've found over the last two days
> should be solved completely by what you have queued for Arnd.
OK good to hear.
> One last issue though...
>
> We had this patch:
>
> http://lists.arm.linux.org.uk/lurker/message/20111006.232441.227dfcf6.en.html
>
> which is from Paul, post my complaint about IS_ERR_VALUE being used.
> This removed sr1_hwmod and sr2_hwmod, and the commit message explicitly
> talks about doing this.
>
> There's also the patch below. Somehow, this resulted in that bit of
> Paul's patch being removed (possibly automatically by git) but the commit
> comments are retained, which are now stale and no longer reflect what the
> patch is doing... That's rather unfortunate, but at this point its
> probably too late to do something about it.
Yeah that's a bit unfortunate. At least the commit message mentions
what it fixes, and then mentions the secondary bug related to the
sr[12]_hwmod entries. Anyways, I'd rather not start messing with commit
unless people think it's worth rebasing about half of the patches
in fixes.
Regards,
Tony
next prev parent reply other threads:[~2011-11-07 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 17:56 [PATCH] arm: omap2+: hwmod: fix breakage introduced by d6504acd Felipe Balbi
2011-11-07 18:32 ` Russell King - ARM Linux
2011-11-07 19:39 ` Felipe Balbi
2011-11-07 21:27 ` Russell King - ARM Linux
2011-11-07 21:29 ` Paul Walmsley
2011-11-07 22:41 ` Russell King - ARM Linux
2011-11-07 22:51 ` Tony Lindgren
2011-11-07 22:55 ` Russell King - ARM Linux
2011-11-07 23:07 ` Tony Lindgren
2011-11-07 23:16 ` Russell King - ARM Linux
2011-11-07 23:27 ` Tony Lindgren [this message]
2011-11-07 21:30 ` Paul Walmsley
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=20111107232713.GD31337@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