All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP4: wakeupgen: remove duplicate AUXCOREBOOT* read/write
Date: Tue, 11 Sep 2012 11:49:45 -0700	[thread overview]
Message-ID: <20120911184945.GO23092@atomide.com> (raw)
In-Reply-To: <CAMQu2gxkQ1JAjbuhFZqUxgrgzrFLhMZk_Q8TzXW5q9Lr3JOmqQ@mail.gmail.com>

* Shilimkar, Santosh <santosh.shilimkar@ti.com> [120911 00:20]:
> On Tue, Sep 11, 2012 at 12:13 PM, Paul Walmsley <paul@pwsan.com> wrote:
> > On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
> >
> >> On Tue, Sep 11, 2012 at 12:07 PM, Paul Walmsley <paul@pwsan.com> wrote:
> >> > On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
> >> >
> >> >> On Tue, Sep 11, 2012 at 12:25 AM, Tony Lindgren <tony@atomide.com> wrote:
> >> >> > * Shilimkar, Santosh <santosh.shilimkar@ti.com> [120908 01:20]:
> >> >> >>
> >> >> >> Will you able to pick up these couple of wakeupgen fixes from  here or
> >> >> >> do you want me to send you a pull request for 3.6-rc5/6
> >> >> >
> >> >> > I can pick them into fixes-noncritical. But if the second one is
> >> >> > a major bug for the -rc series, the patch should be describe what
> >> >> > breaks (regression? oops?).
> >> >> >
> >> >> Fixes non critical is fine. No major issue without these patches.
> >> >
> >> > There's an ordering constraint though: Santosh's patch needs to go in
> >> > first, then mine.
> >> >
> >> Its other way round ;-)
> >> Mine I created after applying your change.
> >
> > The problem is that if my patch is applied first, then there will be a
> > point after my patch where the AUXCOREBOOT1 register won't be saved, which
> > might break PM.  So the patches may need to be updated.
> >
> Good point. It's trivial to re-order them.
> 
> Tony,
> Updated patches in the end of the email. Also attached.

Thanks applying into fixes-non-critical.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP4: wakeupgen: remove duplicate AUXCOREBOOT* read/write
Date: Tue, 11 Sep 2012 11:49:45 -0700	[thread overview]
Message-ID: <20120911184945.GO23092@atomide.com> (raw)
In-Reply-To: <CAMQu2gxkQ1JAjbuhFZqUxgrgzrFLhMZk_Q8TzXW5q9Lr3JOmqQ@mail.gmail.com>

* Shilimkar, Santosh <santosh.shilimkar@ti.com> [120911 00:20]:
> On Tue, Sep 11, 2012 at 12:13 PM, Paul Walmsley <paul@pwsan.com> wrote:
> > On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
> >
> >> On Tue, Sep 11, 2012 at 12:07 PM, Paul Walmsley <paul@pwsan.com> wrote:
> >> > On Tue, 11 Sep 2012, Shilimkar, Santosh wrote:
> >> >
> >> >> On Tue, Sep 11, 2012 at 12:25 AM, Tony Lindgren <tony@atomide.com> wrote:
> >> >> > * Shilimkar, Santosh <santosh.shilimkar@ti.com> [120908 01:20]:
> >> >> >>
> >> >> >> Will you able to pick up these couple of wakeupgen fixes from  here or
> >> >> >> do you want me to send you a pull request for 3.6-rc5/6
> >> >> >
> >> >> > I can pick them into fixes-noncritical. But if the second one is
> >> >> > a major bug for the -rc series, the patch should be describe what
> >> >> > breaks (regression? oops?).
> >> >> >
> >> >> Fixes non critical is fine. No major issue without these patches.
> >> >
> >> > There's an ordering constraint though: Santosh's patch needs to go in
> >> > first, then mine.
> >> >
> >> Its other way round ;-)
> >> Mine I created after applying your change.
> >
> > The problem is that if my patch is applied first, then there will be a
> > point after my patch where the AUXCOREBOOT1 register won't be saved, which
> > might break PM.  So the patches may need to be updated.
> >
> Good point. It's trivial to re-order them.
> 
> Tony,
> Updated patches in the end of the email. Also attached.

Thanks applying into fixes-non-critical.

Regards,

Tony

  reply	other threads:[~2012-09-11 18:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 23:34 [PATCH] ARM: OMAP4: wakeupgen: remove duplicate AUXCOREBOOT* read/write Paul Walmsley
2012-09-05 23:34 ` Paul Walmsley
2012-09-06  6:35 ` Shilimkar, Santosh
2012-09-06  6:35   ` Shilimkar, Santosh
2012-09-08  8:18   ` Shilimkar, Santosh
2012-09-08  8:18     ` Shilimkar, Santosh
2012-09-10 18:55     ` Tony Lindgren
2012-09-10 18:55       ` Tony Lindgren
2012-09-11  6:19       ` Shilimkar, Santosh
2012-09-11  6:19         ` Shilimkar, Santosh
2012-09-11  6:37         ` Paul Walmsley
2012-09-11  6:37           ` Paul Walmsley
2012-09-11  6:40           ` Shilimkar, Santosh
2012-09-11  6:40             ` Shilimkar, Santosh
2012-09-11  6:43             ` Paul Walmsley
2012-09-11  6:43               ` Paul Walmsley
2012-09-11  7:19               ` Shilimkar, Santosh
2012-09-11  7:19                 ` Shilimkar, Santosh
2012-09-11 18:49                 ` Tony Lindgren [this message]
2012-09-11 18:49                   ` Tony Lindgren

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=20120911184945.GO23092@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.