From: akpm@linux-foundation.org
To: andy.shevchenko@gmail.com, minchan@kernel.org,
mm-commits@vger.kernel.org, nick.desaulniers@gmail.com,
sergey.senozhatsky@gmail.com, willy@infradead.org
Subject: [merged] zsmalloc-use-u-suffix-for-negative-literals-being-shifted.patch removed from -mm tree
Date: Thu, 01 Feb 2018 11:34:13 -0800 [thread overview]
Message-ID: <20180201193413.zekbCoQsd%akpm@linux-foundation.org> (raw)
The patch titled
Subject: zsmalloc: use U suffix for negative literals being shifted
has been removed from the -mm tree. Its filename was
zsmalloc-use-u-suffix-for-negative-literals-being-shifted.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Nick Desaulniers <nick.desaulniers@gmail.com>
Subject: zsmalloc: use U suffix for negative literals being shifted
Fix warning about shifting unsigned literals being undefined behavior.
Link: http://lkml.kernel.org/r/1515642078-4259-1-git-send-email-nick.desaulniers@gmail.com
Signed-off-by: Nick Desaulniers <nick.desaulniers@gmail.com>
Suggested-by: Minchan Kim <minchan@kernel.org>
Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Nick Desaulniers <nick.desaulniers@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/zsmalloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/zsmalloc.c~zsmalloc-use-u-suffix-for-negative-literals-being-shifted mm/zsmalloc.c
--- a/mm/zsmalloc.c~zsmalloc-use-u-suffix-for-negative-literals-being-shifted
+++ a/mm/zsmalloc.c
@@ -1047,7 +1047,7 @@ static void init_zspage(struct size_clas
* Reset OBJ_TAG_BITS bit to last link to tell
* whether it's allocated object or not.
*/
- link->next = -1 << OBJ_TAG_BITS;
+ link->next = -1UL << OBJ_TAG_BITS;
}
kunmap_atomic(vaddr);
page = next_page;
_
Patches currently in -mm which might be from nick.desaulniers@gmail.com are
reply other threads:[~2018-02-01 19:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180201193413.zekbCoQsd%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=nick.desaulniers@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=willy@infradead.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