From: Tony Lindgren <tony@atomide.com> To: arm@kernel.org Cc: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [GIT PULL] Fix omap4 and later lost cpu1 interrupts for periodic timer Date: Thu, 14 Feb 2019 10:01:34 -0800 [thread overview] Message-ID: <pull-1550167274-497763@atomide.com> (raw) From: "Tony Lindgren" <tony@atomide.com> The following changes since commit dc30e70391376ba3987aeb856ae6d9c0706534f1: ARM: OMAP2+: Variable "reg" in function omap4_dsi_mux_pads() could be uninitialized (2019-01-29 08:54:22 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.0/fixes-rc5 for you to fetch changes up to 50d6b3cf9403879911e06d69c7ef41e43f8f7b4b: ARM: OMAP2+: fix lack of timer interrupts on CPU1 after hotplug (2019-02-07 07:48:22 -0800) ---------------------------------------------------------------- Fix omap4 and later lost cpu1 interrupts for periodic timer A fix from Russell that took a while to get applied into fixes as I thought Russell is merging this one. ---------------------------------------------------------------- Russell King (1): ARM: OMAP2+: fix lack of timer interrupts on CPU1 after hotplug arch/arm/mach-omap2/cpuidle44xx.c | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com> To: arm@kernel.org Cc: Tony Lindgren <tony@atomide.com>, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [GIT PULL] Fix omap4 and later lost cpu1 interrupts for periodic timer Date: Thu, 14 Feb 2019 10:01:34 -0800 [thread overview] Message-ID: <pull-1550167274-497763@atomide.com> (raw) From: "Tony Lindgren" <tony@atomide.com> The following changes since commit dc30e70391376ba3987aeb856ae6d9c0706534f1: ARM: OMAP2+: Variable "reg" in function omap4_dsi_mux_pads() could be uninitialized (2019-01-29 08:54:22 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.0/fixes-rc5 for you to fetch changes up to 50d6b3cf9403879911e06d69c7ef41e43f8f7b4b: ARM: OMAP2+: fix lack of timer interrupts on CPU1 after hotplug (2019-02-07 07:48:22 -0800) ---------------------------------------------------------------- Fix omap4 and later lost cpu1 interrupts for periodic timer A fix from Russell that took a while to get applied into fixes as I thought Russell is merging this one. ---------------------------------------------------------------- Russell King (1): ARM: OMAP2+: fix lack of timer interrupts on CPU1 after hotplug arch/arm/mach-omap2/cpuidle44xx.c | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-14 18:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-14 18:01 Tony Lindgren [this message] 2019-02-14 18:01 ` [GIT PULL] Fix omap4 and later lost cpu1 interrupts for periodic timer Tony Lindgren 2019-02-15 17:12 ` Arnd Bergmann 2019-02-15 17:12 ` Arnd Bergmann
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=pull-1550167274-497763@atomide.com \ --to=tony@atomide.com \ --cc=arm@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ /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: linkBe 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.