lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121030191809.GA1868@kroah.com>
Date:	Tue, 30 Oct 2012 12:18:09 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:	Nitin Gupta <ngupta@...are.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] zram: permit sleeping while in pool zs_malloc()

On Tue, Oct 30, 2012 at 09:49:11PM +0300, Sergey Senozhatsky wrote:
> On (10/30/12 11:04), Greg Kroah-Hartman wrote:
> > On Tue, Oct 30, 2012 at 12:03:19PM +0300, Sergey Senozhatsky wrote:
> > >     zram: permit sleeping while in pool zs_malloc()
> > 
> > 2/2?  Huh?  Where is 1/2?
> > 
> > I have a raft of patches from you, all out of order, and full of
> > responses from Nitin, and so, I really have no idea what should and
> > should not be applied here.
> > 
> > So, I'm dropping them all.  Please work with Nitin to get a series of
> > patches that are acceptable and resend them with the proper numbering.
> > 
> 
> those were two separate series.
> 
> the first one:
> 
> [PATCH 1/2] zram: factor-out zram_decompress_page() function
> [PATCH 2/2] zram: handle mem suffixes in disk size zram_sysfs parameter
> 
> ACKed by Nitin.
> 
> 
> 
> the second one
> 
> [PATCH 2/2] zram: permit sleeping while in pool zs_malloc()
> [PATCH 1/2] zram: forbid IO operations from within zram_init_device()  -- droppped by me.
> 
> 
> I'll resend first two and next time will make sure not to spam your box. sorry.

Sending me lots of patches is fine, I don't mind that at all.  It's what
I'm here for it seems :)

But when there is responses, and follow-up patches, and second versions
and lots of other stuff, it gets hard to follow, so I ask for them all
to be resent, like this.

But, what happened with your second series?  As you didn't resend them,
I'll just ignore them for now, please resend if you ever get them worked
out.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ