From: David Howells <dhowells@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dhowells@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] Consolidate init_task handling
Date: Sat, 25 Nov 2017 22:38:17 +0000 [thread overview]
Message-ID: <23236.1511649497@warthog.procyon.org.uk> (raw)
In-Reply-To: <CA+55aFxm=PyGnWHL_jErtDjx9Exmw8MkD7Td+7Hn=6b7XYO=Vw@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> Or at least it's a very unusual use of that word. Why doesn't the
> explanation just say what it does: "move", and say from where to where
> ("from macro to definition" or something)?
>
> Or "remove macro XYZ, expanding it in place", or something? To me,
> "unroll" has a completely different meaning in computers.
I don't remember why I used the word "Unroll", but "Expand X in place" seems a
good substitute.
Do you want me to repost the patches?
David
next prev parent reply other threads:[~2017-11-25 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 15:31 David Howells
2017-11-24 15:31 ` [PATCH 1/5] Construct init thread stack in the linker script rather than by union David Howells
2017-11-24 15:32 ` [PATCH 2/5] Unroll INIT_TASK() in init/init_task.c David Howells
2017-11-24 15:32 ` [PATCH 3/5] Unroll various INIT_* macros David Howells
2017-11-24 15:32 ` [PATCH 4/5] Unroll the INIT_SIGNALS and INIT_SIGHAND macros David Howells
2017-11-24 15:32 ` [PATCH 5/5] Unroll INIT_STRUCT_PID David Howells
2017-11-25 2:18 ` [PATCH 0/5] Consolidate init_task handling Linus Torvalds
2017-11-25 22:38 ` David Howells [this message]
2017-11-25 22:47 ` David Howells
2017-11-26 23:08 ` Linus Torvalds
2017-11-26 23:44 ` David Howells
2017-11-26 23:50 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2017-07-20 12:50 David Howells
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=23236.1511649497@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®