From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Richard Weinberger <richard@nod.at>,
David Miller <davem@davemloft.net>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH v2] all arches, signal: Move restart_block to struct task_struct
Date: Wed, 3 Dec 2014 15:53:52 -0800 [thread overview]
Message-ID: <20141203155352.ea5322ff45c6200238c7ef51@linux-foundation.org> (raw)
In-Reply-To: <CALCETrVk0EBL0vk8kjOhjkMAOaxXukCdSptzfHU=g1s7JChXiQ@mail.gmail.com>
On Wed, 3 Dec 2014 15:38:29 -0800 Andy Lutomirski <luto@amacapital.net> wrote:
> Yes, exactly.
>
> >
> > Spelling this out in the changelog would be useful for the ignorant and
> > the forgetful ;)
>
> Want a new version, or will you fix it up yourself?
>
I think I can work that out.
A couple of linux-next things to check:
- arch/arm/include/asm/thread_info.h:arm_restart_block has
disappeared from the thread_info.
- the reference to ti->restart_block in arch/arm/kernel/traps.c has
vanished. I couldn't find anywhere where it was moved to.
next prev parent reply other threads:[~2014-12-03 23:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 17:36 [PATCH v2] all arches, signal: Move restart_block to struct task_struct Andy Lutomirski
2014-10-29 18:12 ` Thomas Gleixner
2014-10-29 18:12 ` Thomas Gleixner
2014-11-10 22:03 ` Andy Lutomirski
2014-11-11 2:13 ` David Miller
2014-11-11 2:13 ` David Miller
2014-11-11 10:52 ` Richard Weinberger
2014-12-01 14:55 ` Andy Lutomirski
2014-12-01 14:55 ` Andy Lutomirski
2014-12-03 23:37 ` Andrew Morton
2014-12-03 23:37 ` Andrew Morton
2014-12-03 23:38 ` Andy Lutomirski
2014-12-03 23:53 ` Andrew Morton [this message]
2014-12-04 0:01 ` Andy Lutomirski
2014-12-04 0:01 ` Andy Lutomirski
2014-12-05 11:13 ` Chuck Ebbert
2014-12-08 22:51 ` Andy Lutomirski
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=20141203155352.ea5322ff45c6200238c7ef51@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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