linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jeremy Vial <jvial@adeneo-embedded.com>
Cc: linux-omap@vger.kernel.org, linux@arm.linux.org.uk,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Manage OMAP34xx ES3.1.2 rev to resume from suspend
Date: Fri, 1 Aug 2014 01:21:41 -0700	[thread overview]
Message-ID: <20140801082140.GA26699@atomide.com> (raw)
In-Reply-To: <1406812234-23163-1-git-send-email-jvial@adeneo-embedded.com>

* Jeremy Vial <jvial@adeneo-embedded.com> [140731 06:16]:
> Hi,
> 
> My kernel crashed when my OMAP34xx ES3.1.2 leave suspend mode. The first
> patch seems to solve the issue, and the second one corrects Linux kernel
> coding style problems.
> 
> Jeremy Vial (2):
>   ARM: OMAP3: Fix choice of omap3_restore_es function in OMAP34XX
>     rev3.1.2 case.
>   ARM: OMAP3: Fix coding style problems in
>     arch/arm/mach-omap2/control.c
> 
>  arch/arm/mach-omap2/control.c |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Thanks applying these fixes for the merge window. I've tagged
the first patch also for stable.

Regards,

Tony

      parent reply	other threads:[~2014-08-01  8:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 13:10 [PATCH 0/2] Manage OMAP34xx ES3.1.2 rev to resume from suspend Jeremy Vial
2014-07-31 13:10 ` [PATCH 1/2] ARM: OMAP3: Fix choice of omap3_restore_es function in OMAP34XX rev3.1.2 case Jeremy Vial
2014-07-31 13:10 ` [PATCH 2/2] ARM: OMAP3: Fix coding style problems in arch/arm/mach-omap2/control.c Jeremy Vial
2014-08-01  8:21 ` Tony Lindgren [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=20140801082140.GA26699@atomide.com \
    --to=tony@atomide.com \
    --cc=jvial@adeneo-embedded.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).