linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the omap-fixes tree
Date: Wed, 11 Nov 2020 09:21:11 +0200	[thread overview]
Message-ID: <20201111072111.GP26857@atomide.com> (raw)
In-Reply-To: <20201111081613.0f2ce62a@canb.auug.org.au>

* Stephen Rothwell <sfr@canb.auug.org.au> [201110 21:16]:
> Hi all,
> 
> In commit
> 
>   e4b5575da267 ("ARM: OMAP2+: Manage MPU state properly for omap_enter_idle_coupled()")
> 
> Fixes tag
> 
>   Fixes: 8ca5ee624b4c ("ARM: OMAP2+: Restore MPU power domain if cpu_cluster_pm_enter() fails")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meeant
> 
> Fixes: 8f04aea048d5 ("ARM: OMAP2+: Restore MPU power domain if cpu_cluster_pm_enter() fails")

Thanks for catching it, will fix!

Tony


  reply	other threads:[~2020-11-11  7:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 21:16 linux-next: Fixes tag needs some work in the omap-fixes tree Stephen Rothwell
2020-11-11  7:21 ` Tony Lindgren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-12 21:02 Stephen Rothwell
2022-04-13  6:21 ` H. Nikolaus Schaller
2022-04-14  8:46   ` Tony Lindgren
2019-12-17 20:13 Stephen Rothwell
2019-12-17 23:23 ` Tony Lindgren
2019-09-10 14:08 Stephen Rothwell
2019-09-10 14:32 ` Tony Lindgren
2019-01-23  5:32 Stephen Rothwell
2019-01-23 21:14 ` 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=20201111072111.GP26857@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).