From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754554AbbI3IS3 (ORCPT ); Wed, 30 Sep 2015 04:18:29 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:32990 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753063AbbI3ISY (ORCPT ); Wed, 30 Sep 2015 04:18:24 -0400 MIME-Version: 1.0 In-Reply-To: <20150930081304.GE12727@bbox> References: <20150914154901.92c5b7b24e15f04d8204de18@gmail.com> <20150915061349.GA16485@bbox> <20150930075203.GC12727@bbox> <20150930081304.GE12727@bbox> Date: Wed, 30 Sep 2015 10:18:23 +0200 Message-ID: Subject: Re: [PATCH 0/3] allow zram to use zbud as underlying allocator From: Vitaly Wool To: Minchan Kim Cc: Sergey Senozhatsky , Dan Streetman , LKML , Linux-MM , =?UTF-8?B?6rmA7KSA7IiY?= , Gioh Kim , Vlastimil Babka Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 30, 2015 at 10:13 AM, Minchan Kim wrote: > On Wed, Sep 30, 2015 at 10:01:59AM +0200, Vitaly Wool wrote: >> > Could you share your script? >> > I will ask our production team to reproduce it. >> >> Wait, let me get it right. Your production team? >> I take it as you would like me to help your company fix your bugs. >> You are pushing the limits here. > > I'm really sorry if you take it as fixing my bugs. > I never wanted it but just want to help your problem. > Please read LKML. Normally, developers wanted to share test script to > reproduce the problem because it's easier to solve the problem > without consuming much time with ping-pong. Normally developers do not have backing up "production teams". > Anyway, I have shared my experience to you and suggest patches and > on-going works. In your concept, I shouldn't do that for fixing > your problems so I shouldn't help you any more? Right? I never asked you to fix my problems. I have substantial proof that zsmalloc is fragile enough not to be a good fit for projects I work on and I want to have the code that allows zram to work with zbud mainlined. Whatever you want me to do to help you fix zsmalloc issues *should* be *orthogonal* to the former. You are abusing your maintainer role here, trying to act in favor of your company rather than for the benefit of OSS. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by kanga.kvack.org (Postfix) with ESMTP id D165A6B0038 for ; Wed, 30 Sep 2015 04:18:24 -0400 (EDT) Received: by wiclk2 with SMTP id lk2so49675018wic.1 for ; Wed, 30 Sep 2015 01:18:24 -0700 (PDT) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com. [2a00:1450:400c:c05::234]) by mx.google.com with ESMTPS id hv7si34824906wjb.43.2015.09.30.01.18.23 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Sep 2015 01:18:23 -0700 (PDT) Received: by wicfx3 with SMTP id fx3so49601468wic.0 for ; Wed, 30 Sep 2015 01:18:23 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20150930081304.GE12727@bbox> References: <20150914154901.92c5b7b24e15f04d8204de18@gmail.com> <20150915061349.GA16485@bbox> <20150930075203.GC12727@bbox> <20150930081304.GE12727@bbox> Date: Wed, 30 Sep 2015 10:18:23 +0200 Message-ID: Subject: Re: [PATCH 0/3] allow zram to use zbud as underlying allocator From: Vitaly Wool Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: Minchan Kim Cc: Sergey Senozhatsky , Dan Streetman , LKML , Linux-MM , =?UTF-8?B?6rmA7KSA7IiY?= , Gioh Kim , Vlastimil Babka On Wed, Sep 30, 2015 at 10:13 AM, Minchan Kim wrote: > On Wed, Sep 30, 2015 at 10:01:59AM +0200, Vitaly Wool wrote: >> > Could you share your script? >> > I will ask our production team to reproduce it. >> >> Wait, let me get it right. Your production team? >> I take it as you would like me to help your company fix your bugs. >> You are pushing the limits here. > > I'm really sorry if you take it as fixing my bugs. > I never wanted it but just want to help your problem. > Please read LKML. Normally, developers wanted to share test script to > reproduce the problem because it's easier to solve the problem > without consuming much time with ping-pong. Normally developers do not have backing up "production teams". > Anyway, I have shared my experience to you and suggest patches and > on-going works. In your concept, I shouldn't do that for fixing > your problems so I shouldn't help you any more? Right? I never asked you to fix my problems. I have substantial proof that zsmalloc is fragile enough not to be a good fit for projects I work on and I want to have the code that allows zram to work with zbud mainlined. Whatever you want me to do to help you fix zsmalloc issues *should* be *orthogonal* to the former. You are abusing your maintainer role here, trying to act in favor of your company rather than for the benefit of OSS. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org