From: Andrew Morton <akpm@linux-foundation.org>
To: cpw@sgi.com (Cliff Wickman)
Cc: linux-kernel@vger.kernel.org, pj@sgi.com, clameter@sgi.com,
rientjes@google.com, menage@google.com, cpw@sgi.com,
Lee.Schermerhorn@hp.com
Subject: Re: [PATCH 2/4 v2] hotplug cpu move tasks in empty cpusets to parent various other fixes
Date: Mon, 4 Feb 2008 13:56:06 -0800 [thread overview]
Message-ID: <20080204135606.b6e1a065.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080204174051.ACC3F1FE109@attica.americas.sgi.com>
Confused.
On Mon, 04 Feb 2008 11:40:51 -0600
cpw@sgi.com (Cliff Wickman) wrote:
> From: cpw@sgi.com (Cliff Wickman)
> To: linux-kernel@vger.kernel.org
> Cc: pj@sgi.com, clameter@sgi.com, rientjes@google.com, menage@google.com, cpw@sgi.com, Lee.Schermerhorn@hp.com, akpm@linux-foundation.org
> Subject: [PATCH 2/4 v2] hotplug cpu move tasks in empty cpusets to parent various other fixes
> Date: Mon, 04 Feb 2008 11:40:51 -0600
> User-Agent: nail 11.25 7/29/05
>
>
The above implies that the patch was authored by Cliff.
> Various minor formatting and comment tweaks to Cliff Wickman's
> [PATCH_3_of_3]_cpusets__update_cpumask_revision.patch
>
> I had had "iff", meaning "if and only if" in a comment.
And the "I" here implies that the patch was authored by Cliff.
> However, except for ancient mathematicians, the abbreviation
> "iff" was a tad too cryptic. Cliff changed it to "if",
> presumably figuring that the "iff" was a typo. However, it
> was the "only if" half of the conjunction that was most
> interesting. Reword to emphasis the "only if" aspect.
>
> The locking comment for remove_tasks_in_empty_cpuset() was wrong;
> it said callback_mutex had to be held on entry. The opposite
> is true.
>
> Several mentions of attach_task() in comments needed to be
> changed to cgroup_attach_task().
>
> A comment about notify_on_release was no longer relevant,
> as the line of code it had commented, namely:
> set_bit(CS_RELEASED_RESOURCE, &parent->flags);
> is no longer present in that place in the cpuset.c code.
>
> Similarly a comment about notify_on_release before the
> scan_for_empty_cpusets() routine was no longer relevant.
>
> Removed extra parentheses and unnecessary return statement.
>
> Renamed attach_task() to cpuset_attach() in various comments.
>
> Removed comment about not needing memory migration, as it
> seems the migration is done anyway, via the cpuset_attach()
> callback from cgroup_attach_task().
>
> Signed-off-by: Paul Jackson <pj@sgi.com>
> Acked-by: Cliff Wickman <cpw@sgi.com>
But the signoffs imply that Paul was the author.
I'm going to assume it was Paul.
We indicate authorship by putting a "From: foo <bar@zot.com>" at the very
first line of the changelog. If that is absent then we use the From: from email
headers.
Please remember to do this - it is more reliable than akpm forensics.
next prev parent reply other threads:[~2008-02-04 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 17:40 Cliff Wickman
2008-02-04 21:56 ` Andrew Morton [this message]
2008-02-04 22:02 ` Paul Jackson
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=20080204135606.b6e1a065.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Lee.Schermerhorn@hp.com \
--cc=clameter@sgi.com \
--cc=cpw@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=pj@sgi.com \
--cc=rientjes@google.com \
/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®