From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCHv3 0/8] introduce dynamic device creation/removal
Date: Thu, 16 Apr 2015 09:47:44 +0900 [thread overview]
Message-ID: <20150416004744.GB2018@swordfish> (raw)
In-Reply-To: <20150415143717.3c94969fbaef635d7afae9eb@linux-foundation.org>
On (04/15/15 14:37), Andrew Morton wrote:
> Unfortunately these were the first-arriving zram patches, so the later
> ones required quite a bit of mangling. Hopefully I got it all right.
>
> This was all a bit disruptive. Please let's not leave major patchsets
> floating about in an incomplete/unresolved state for week after week?
>
Andrew, sorry for confusion.
I will fold/cleanup and resend the whole patchset. sorry for
I currently have:
0001-zram-cosmetic-ZRAM_ATTR_RO-code-formatting-tweak.patch
0002-zram-use-idr-instead-of-zram_devices-array.patch
0003-zram-factor-out-device-reset-from-reset_store.patch
0004-zram-reorganize-code-layout.patch
0005-zram-add-dynamic-device-add-remove-functionality.patch
0006-zram-add-dynamic-device-add-remove-functionality-fix.patch
0007-zram-remove-max_num_devices-limitation.patch
0008-zram-report-every-added-and-removed-device.patch
0009-zram-trivial-correct-flag-operations-comment.patch
0010-zram-return-zram-device_id-value-from-zram_add.patch
0011-zram-introduce-automatic-device_id-generation.patch
0012-zram-introduce-automatic-device_id-generation-fix.patch
0013-zram-do-not-let-user-enforce-new-device-dev_id.patch
0014-zram-support-compaction.patch
0015-zram-remove-num_migrated-device-attr.patch
0016-zram-move-compact_store-to-sysfs-functions-area.patch
0017-zram-use-generic-start-end-io-accounting.patch
0018-zram-export-new-io_stat-sysfs-attrs.patch
0019-zram-export-new-mm_stat-sysfs-attrs.patch
0020-zram-deprecate-zram-attrs-sysfs-nodes.patch
0021-zram-fix-error-return-code.patch
in my tree. the resulting patchset will be smaller in size.
I'll send it out later this day.
-ss
prev parent reply other threads:[~2015-04-16 0:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 12:49 [PATCHv3 0/8] introduce dynamic device creation/removal Sergey Senozhatsky
2015-03-03 12:49 ` [PATCH 1/8] zram: cosmetic ZRAM_ATTR_RO code formatting tweak Sergey Senozhatsky
2015-03-03 12:49 ` [PATCH 2/8] zram: use idr instead of `zram_devices' array Sergey Senozhatsky
2015-03-03 22:01 ` Andrew Morton
2015-03-04 0:21 ` Sergey Senozhatsky
2015-03-04 7:06 ` Minchan Kim
2015-03-04 7:34 ` Sergey Senozhatsky
2015-03-04 7:49 ` Sergey Senozhatsky
2015-03-05 0:59 ` Minchan Kim
2015-03-03 12:49 ` [PATCH 3/8] zram: factor out device reset from reset_store() Sergey Senozhatsky
2015-03-05 2:28 ` Minchan Kim
2015-03-03 12:49 ` [PATCH 4/8] zram: reorganize code layout Sergey Senozhatsky
2015-03-03 12:49 ` [PATCH 5/8] zram: add dynamic device add/remove functionality Sergey Senozhatsky
2015-03-03 22:01 ` Andrew Morton
2015-03-04 0:18 ` Sergey Senozhatsky
2015-03-04 7:10 ` Minchan Kim
2015-03-04 7:29 ` Sergey Senozhatsky
2015-03-04 8:19 ` Sergey Senozhatsky
2015-03-04 8:36 ` Sergey Senozhatsky
2015-03-03 12:49 ` [PATCH 6/8] zram: remove max_num_devices limitation Sergey Senozhatsky
2015-03-03 12:49 ` [PATCH 7/8] zram: report every added and removed device Sergey Senozhatsky
2015-03-03 12:49 ` [PATCH 8/8] zram: trivial: correct flag operations comment Sergey Senozhatsky
2015-04-15 21:37 ` [PATCHv3 0/8] introduce dynamic device creation/removal Andrew Morton
2015-04-15 23:40 ` Minchan Kim
2015-04-16 0:30 ` Sergey Senozhatsky
2015-04-16 0:47 ` Sergey Senozhatsky [this message]
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=20150416004744.GB2018@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.