All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	lwn@lwn.net
Subject: Re: Linux 4.1.28
Date: Thu, 14 Jul 2016 19:58:22 +0200	[thread overview]
Message-ID: <s5hy454cda9.wl-tiwai@suse.de> (raw)
In-Reply-To: <5786F7BC.9090406@oracle.com>

Hi Sasha,

On Thu, 14 Jul 2016 04:23:56 +0200,
Sasha Levin wrote:
> 
> I'm announcing the release of the 4.1.28 kernel.
> 
> All users of the 4.1 kernel series must upgrade.
> 
> The updated 4.1.y git tree can be found at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.1.y
> and can be browsed at the normal kernel.org git web browser:
> 	http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary

This kernel gives a build failure on ppc64le:

 arch/powerpc/kernel/prom.c:170:25: error: 'PPC_FEATURE2_HTM_NOSC_COMP' undeclared here (not in a function)
   PPC_FEATURE2_HTM_COMP|PPC_FEATURE2_HTM_NOSC_COMP, 22, 0, 0},
                         ^

It's due to the commit f49eb503f0f9ab66874a81992b14249a1c59b6ad
    powerpc: Update TM user feature bits in scan_features()

FYI, the macro referred there is defined in the upstream commit
b4b56f9ecab40f3b4ef53e130c9f6663be491894
    powerpc/tm: Abort syscalls in active transactions

Please revert the relevant commit, or fix it properly.


thanks,

Takashi

  reply	other threads:[~2016-07-14 17:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14  2:23 Linux 4.1.28 Sasha Levin
2016-07-14 17:58 ` Takashi Iwai [this message]
2016-07-15 11:38 ` Thomas Voegtle
2016-07-15 11:54   ` Sasha Levin
2016-07-15 13:04     ` Thomas Voegtle
2016-07-20  6:45       ` Arkadiusz Miskiewicz
2016-07-20  7:03         ` Arkadiusz Miskiewicz
2016-07-20  8:29       ` Michal Kubecek
2016-07-20 12:13         ` Thomas Voegtle
2016-08-02 16:14         ` Thomas Voegtle
2016-08-02 17:02           ` Michal Kubecek
2016-07-29 17:24     ` Josh Hunt

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=s5hy454cda9.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=sasha.levin@oracle.com \
    --cc=stable@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: 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.