All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@list.ru>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Helge Deller <deller@gmx.de>, David Miller <davem@davemloft.net>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] sigaltstack: support SS_AUTODISARM for CONFIG_COMPAT
Date: Mon, 6 Feb 2017 12:30:38 +0300	[thread overview]
Message-ID: <9954a03a-5afd-f441-a784-5eb3304d6c3f@list.ru> (raw)
In-Reply-To: <CALCETrVvKeGGN_eb9_t9KDvDVB8WFM6uZTVsKJLx6TvJ4FrrYw@mail.gmail.com>

05.02.2017 21:31, Andy Lutomirski пишет:
> On Sun, Feb 5, 2017 at 2:12 AM, Stas Sergeev <stsp@list.ru> wrote:
>> Currently SS_AUTODISARM is not supported in compatibility
>> mode, but does not return -EINVAL either. This makes dosemu
>> built with -m32 on x86_64 to crash. Also the kernel's sigaltstack
>> selftest fails if compiled with -m32.
>>
>> This patch adds the needed support.
>>
>> Suggesting for -stable.
> This looks correct.
So it seems my patches haven't made it into LKML
and I don't know if they made it into stable@ because
the archive link:
http://dir.gmane.org/gmane.linux.kernel.stable
doesn't work.
There is definitely something wrong here.

So did they pass into a stable ML?
If not, Andy can I use your Acked-by when/if resending?
Are there any known problems with MLs and the archives now?

  reply	other threads:[~2017-02-06  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 10:12 [PATCH v2 0/2] sigaltstack: SS_AUTODISARM fixes Stas Sergeev
     [not found] ` <20170205101213.8163-2-stsp@list.ru>
2017-02-05 18:31   ` [PATCH 1/2] sigaltstack: support SS_AUTODISARM for CONFIG_COMPAT Andy Lutomirski
2017-02-06  9:30     ` Stas Sergeev [this message]
2017-02-07  0:04       ` Andrew Morton
2017-02-07  8:55         ` [PATCH 2/2] tests: improve output of sigaltstack testcase Stas Sergeev

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=9954a03a-5afd-f441-a784-5eb3304d6c3f@list.ru \
    --to=stsp@list.ru \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    /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.