linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Borislav Petkov <bp@alien8.de>, Stas Sergeev <stsp@list.ru>
Subject: Re: [PATCH 0/4] SS_AUTODISARM fixes and an ABI change
Date: Wed, 4 May 2016 08:25:19 +0200	[thread overview]
Message-ID: <20160504062519.GA9499@gmail.com> (raw)
In-Reply-To: <cover.1462296606.git.luto@kernel.org>


* Andy Lutomirski <luto@kernel.org> wrote:

> The first three are fixes IMO.  The fourth changes the SS_AUTODISARM
> bit.  I'm assuming that's okay, as the bit has existed in -tip for
> less than a day.

Yeah, it's absolutely OK - I made it a standalone tree so we could even rebase it, 
but I think authorship and intent is clearer with your series on top of Stas's 
original commits.

Thanks,

	Ingo

      parent reply	other threads:[~2016-05-04  6:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 17:31 [PATCH 0/4] SS_AUTODISARM fixes and an ABI change Andy Lutomirski
2016-05-03 17:31 ` [PATCH 1/4] signals/sigaltstack: If SS_AUTODISARM, bypass on_sig_stack Andy Lutomirski
2016-05-04  6:32   ` Ingo Molnar
2016-05-04 23:02     ` Andy Lutomirski
2016-05-04  7:12   ` [tip:core/signals] signals/sigaltstack: If SS_AUTODISARM, bypass on_sig_stack() tip-bot for Andy Lutomirski
2016-05-07 14:37   ` [PATCH 1/4] signals/sigaltstack: If SS_AUTODISARM, bypass on_sig_stack Stas Sergeev
2016-05-09  1:32     ` Andy Lutomirski
2016-05-09  2:04       ` Stas Sergeev
2016-05-14  4:18         ` Andy Lutomirski
2016-05-14 11:18           ` Stas Sergeev
2016-05-14 16:35             ` Andy Lutomirski
2016-05-03 17:31 ` [PATCH 2/4] selftests/sigaltstack: Fix the sas test on old kernels Andy Lutomirski
2016-05-04  7:13   ` [tip:core/signals] selftests/sigaltstack: Fix the sigaltstack " tip-bot for Andy Lutomirski
2016-05-07 15:02   ` [PATCH 2/4] selftests/sigaltstack: Fix the sas " Stas Sergeev
2016-05-09  1:32     ` Andy Lutomirski
2016-05-03 17:31 ` [PATCH 3/4] signals/sigaltstack: Report current flag bits in sigaltstack() Andy Lutomirski
2016-05-04  6:33   ` Ingo Molnar
2016-05-04  7:13   ` [tip:core/signals] " tip-bot for Andy Lutomirski
2016-05-03 17:31 ` [PATCH 4/4] signals/sigaltstack: Change SS_AUTODISARM to (1U << 31) Andy Lutomirski
2016-05-04  7:13   ` [tip:core/signals] " tip-bot for Andy Lutomirski
2016-05-07 15:16   ` [PATCH 4/4] " Stas Sergeev
2016-05-04  6:25 ` Ingo Molnar [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=20160504062519.GA9499@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=stsp@list.ru \
    --cc=x86@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 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).