From: Archit Taneja <a0393947@ti.com>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: tomi.valkeinen@ti.com, jaswinder.singh@linaro.org,
jw@terrafix.co.uk, linux-fbdev@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] OMAPDSS: PM runtime fixes for 3.5-rc
Date: Mon, 09 Jul 2012 07:59:40 +0000 [thread overview]
Message-ID: <4FFA8C9C.2080303@ti.com> (raw)
In-Reply-To: <4FFA0549.9020802@gmx.de>
Hi Florian,
On Monday 09 July 2012 03:40 AM, Florian Tobias Schandinat wrote:
> Hi Archit,
>
> On 07/04/2012 12:43 PM, Archit Taneja wrote:
>> Hi Florian,
>>
>> These are 2 fixes which Tomi had intended to push for the coming rcs. He is
>> currently on vacation and asked me to post the patches on his behalf.
>>
>> The first patch ensures that system suspend doesn't break on OMAP if DSS is
>> enabled. The second patch prevents some warning backtraces when the kernel is
>> not built with PM runtime.
>>
>> Could you please queue these for the upcoming rc?
>
> as you sent me those patches you should have added your Signed-off-by as
> well, I added it.
> Also the first patch of this series contained 2 coding style issues
> related to braces that checkpatch complained about and also differed
> from the coding style used in those files, I fixed those as well.
> I applied both patches.
>
Thanks for the fixes and the pull. I'll be more careful the next time.
Thanks,
Archit
prev parent reply other threads:[~2012-07-09 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:55 [PATCH 0/2] OMAPDSS: PM runtime fixes for 3.5-rc Archit Taneja
2012-07-04 12:55 ` [PATCH 1/2] OMAPDSS: Use PM notifiers for system suspend Archit Taneja
2012-07-04 12:55 ` [PATCH 2/2] OMAPDSS: fix warnings if CONFIG_PM_RUNTIME=n Archit Taneja
2012-07-08 22:10 ` [PATCH 0/2] OMAPDSS: PM runtime fixes for 3.5-rc Florian Tobias Schandinat
2012-07-09 7:59 ` Archit Taneja [this message]
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=4FFA8C9C.2080303@ti.com \
--to=a0393947@ti.com \
--cc=FlorianSchandinat@gmx.de \
--cc=jaswinder.singh@linaro.org \
--cc=jw@terrafix.co.uk \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).