From: Minchan Kim <minchan@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>, akpm@linux-foundation.org
Cc: gregkh@linuxfoundation.org, jeyu@kernel.org, ngupta@vflare.org,
sergey.senozhatsky.work@gmail.com, rafael@kernel.org,
axboe@kernel.dk, tj@kernel.org, mbenes@suse.com,
jpoimboe@redhat.com, tglx@linutronix.de, keescook@chromium.org,
jikos@kernel.org, rostedt@goodmis.org, peterz@infradead.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/2] zram: fix few sysfs races
Date: Thu, 1 Jul 2021 23:01:15 -0700 [thread overview]
Message-ID: <YN6rq03Mf+eSrL43@google.com> (raw)
In-Reply-To: <20210702043716.2692247-1-mcgrof@kernel.org>
On Thu, Jul 01, 2021 at 09:37:14PM -0700, Luis Chamberlain wrote:
> This v5 modifies the second patch, the set of macros needed a bit of
> adjustments so we can keep the same name attributes. It also updates
> the patches to fix all checkpatch complaints.
>
> Luis Chamberlain (2):
> zram: fix crashes with cpu hotplug multistate
> zram: fix deadlock with sysfs attribute usage and module removal
>
> drivers/block/zram/zram_drv.c | 108 ++++++++++++++++++++++++++--------
> drivers/block/zram/zram_drv.h | 54 +++++++++++++++++
> 2 files changed, 137 insertions(+), 25 deletions(-)
Guess first patch would be confilict with recent kernel.
Anyway, please send the patchset with Andrew If he doesn't
pick in a few days.
next prev parent reply other threads:[~2021-07-02 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 4:37 [PATCH v5 0/2] zram: fix few sysfs races Luis Chamberlain
2021-07-02 4:37 ` [PATCH v5 1/2] zram: fix crashes with cpu hotplug multistate Luis Chamberlain
2021-07-02 4:37 ` [PATCH v5 2/2] zram: fix deadlock with sysfs attribute usage and module removal Luis Chamberlain
2021-07-02 5:58 ` Minchan Kim
2021-07-02 7:11 ` Greg KH
2021-07-02 6:01 ` Minchan Kim [this message]
2021-07-02 19:36 ` [PATCH v5 0/2] zram: fix few sysfs races Luis Chamberlain
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=YN6rq03Mf+eSrL43@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.com \
--cc=mcgrof@kernel.org \
--cc=ngupta@vflare.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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