From: Tony Lindgren <tony@atomide.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3 CPUidle patches - fixes
Date: Tue, 5 Aug 2008 11:33:49 +0300 [thread overview]
Message-ID: <20080805083348.GB7193@atomide.com> (raw)
In-Reply-To: <02fd01c8f6bc$fbe96280$74f6180a@wipultra1382>
* Rajendra Nayak <rnayak@ti.com> [080805 08:35]:
>
> > -----Original Message-----
> > From: Tony Lindgren [mailto:tony@atomide.com]
> > Sent: Monday, August 04, 2008 8:03 PM
> > To: Rajendra Nayak
> > Cc: linux-omap@vger.kernel.org
> > Subject: Re: [PATCH] OMAP3 CPUidle patches - fixes
> >
> > * Rajendra Nayak <rnayak@ti.com> [080703 14:55]:
> > > This patch fixes few of the comments posted on the patch
> > set till now.
> > >
> > > One major fix is the moving of uart clock enable/disable
> > out of the context save path as pointed out by Jouni.
> > > This would leave the UART clcoks disabled in case a CORE
> > OFF was attempted and not achieved.
> >
> > What kernel or patch series this is against? If it's for some
> > patch series that's not applied yet to linux-omap tree, let's
> > merge the fix to the original patch.
>
> I sent another patch set later to the list (dated 18/07/2008)
> "[PATCH 00/11] OMAP3 CPUidle patches - ver 2"
> which is the final patch set for CPUidle which can be merged.
> This patch and all the previous patches on CPUidle can be ignored.
Can you please integrate all the fixes to CPUidle and repost the
whole series one more time?
Thanks,
Tony
next prev parent reply other threads:[~2008-08-05 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 8:37 [PATCH] OMAP3 CPUidle patches - fixes Rajendra Nayak
2008-08-04 14:33 ` Tony Lindgren
2008-08-05 5:34 ` Rajendra Nayak
2008-08-05 8:33 ` Tony Lindgren [this message]
2008-08-05 8:35 ` Rajendra Nayak
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=20080805083348.GB7193@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
/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