The patch titled
Subject: cpumask: remove incorrect information from comment
has been added to the -mm tree. Its filename is
cpumask-remove-incorrect-information-from-comment.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/cpumask-remove-incorrect-information-from-comment.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/cpumask-remove-incorrect-information-from-comment.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Eric Biggers <ebiggers3@xxxxxxxxx>
Subject: cpumask: remove incorrect information from comment
Since commit cdfdef75e795f ("cpumask: only allocate nr_cpumask_bits."),
this comment above cpumask_size() is no longer relevant.
Signed-off-by: Eric Biggers <ebiggers3@xxxxxxxxx>
Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/cpumask.h | 2 --
1 file changed, 2 deletions(-)
diff -puN include/linux/cpumask.h~cpumask-remove-incorrect-information-from-comment include/linux/cpumask.h
--- a/include/linux/cpumask.h~cpumask-remove-incorrect-information-from-comment
+++ a/include/linux/cpumask.h
@@ -607,8 +607,6 @@ static inline int cpulist_parse(const ch
/**
* cpumask_size - size to allocate for a 'struct cpumask' in bytes
- *
- * This will eventually be a runtime variable, depending on nr_cpu_ids.
*/
static inline size_t cpumask_size(void)
{
_
Patches currently in -mm which might be from ebiggers3@xxxxxxxxx are
cpumask-remove-incorrect-information-from-comment.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
