From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756656AbbDOVh2 (ORCPT ); Wed, 15 Apr 2015 17:37:28 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:50111 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753404AbbDOVhT (ORCPT ); Wed, 15 Apr 2015 17:37:19 -0400 Date: Wed, 15 Apr 2015 14:37:17 -0700 From: Andrew Morton To: Sergey Senozhatsky Cc: Minchan Kim , Nitin Gupta , linux-kernel@vger.kernel.org, Sergey Senozhatsky Subject: Re: [PATCHv3 0/8] introduce dynamic device creation/removal Message-Id: <20150415143717.3c94969fbaef635d7afae9eb@linux-foundation.org> In-Reply-To: <1425386990-6339-1-git-send-email-sergey.senozhatsky@gmail.com> References: <1425386990-6339-1-git-send-email-sergey.senozhatsky@gmail.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 3 Mar 2015 21:49:42 +0900 Sergey Senozhatsky wrote: > Hello, > > This patchset introduces zram-control sysfs class, which has two sysfs > attrs: > - zram_add -- add a new specific (device_id) zram device > - zram_remove -- remove a specific (device_id) zram device This patchset and the "make automatic device_id generation possible" still appear to have quite a few unresolved issues. So I'm holding them out of the 4.1 merge window. 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?