linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: "Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
	"Dan Streetman" <ddstreet@ieee.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>, 김준수 <iamjoonsoo.kim@lge.com>,
	"Gioh Kim" <gioh.kim@lge.com>, "Vlastimil Babka" <vbabka@suse.cz>
Subject: Re: [PATCH 0/3] allow zram to use zbud as underlying allocator
Date: Wed, 30 Sep 2015 17:13:04 +0900	[thread overview]
Message-ID: <20150930081304.GE12727@bbox> (raw)
In-Reply-To: <CAMJBoFN3j5eZh4+4dnJya9=8Jo=3O9u+v7g0Ka+aVaQyMOG2ew@mail.gmail.com>

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.

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?

> 
> ~vitaly

  reply	other threads:[~2015-09-30  8:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 13:49 [PATCH 0/3] allow zram to use zbud as underlying allocator Vitaly Wool
2015-09-14 13:50 ` [PATCH 1/3] zram: make max_zpage_size configurable Vitaly Wool
2015-09-15  1:00   ` Sergey Senozhatsky
     [not found]     ` <CAMJBoFPynFJpu57Gftm6bbyGfdSK67y-HbvoQPwyuHS6+0tOyQ@mail.gmail.com>
2015-09-15  7:38       ` Sergey Senozhatsky
2015-09-15  5:42   ` Dan Streetman
2015-09-15  6:08     ` Sergey Senozhatsky
2015-09-14 13:51 ` [PATCH 2/3] zpool/zsmalloc/zbud: align on interfaces Vitaly Wool
2015-09-15  1:06   ` Sergey Senozhatsky
2015-09-15  5:09     ` Dan Streetman
2015-09-14 13:55 ` [PATCH 3/3] zram: use common zpool interface Vitaly Wool
2015-09-15  1:12   ` Sergey Senozhatsky
2015-09-15  6:03     ` Dan Streetman
2015-09-14 14:01 ` [PATCH 0/3] allow zram to use zbud as underlying allocator Vlastimil Babka
2015-09-14 14:12   ` Vitaly Wool
2015-09-14 14:14     ` Vlastimil Babka
2015-09-15  4:08       ` Dan Streetman
2015-09-15  4:22         ` Sergey Senozhatsky
2015-09-17  6:21           ` Vlastimil Babka
2015-09-17  9:19             ` Sergey Senozhatsky
2015-09-15  0:49 ` Sergey Senozhatsky
2015-09-15  6:13 ` Minchan Kim
2015-09-25  9:54   ` Vitaly Wool
2015-09-30  7:52     ` Minchan Kim
2015-09-30  8:01       ` Vitaly Wool
2015-09-30  8:13         ` Minchan Kim [this message]
2015-09-30  8:18           ` Vitaly Wool
2015-09-30 15:37     ` Vlastimil Babka
2015-09-30 15:46       ` Vitaly Wool
2015-10-01  7:52         ` Vlastimil Babka
2015-10-10  9:33           ` Vitaly Wool
2015-10-14 13:28             ` Vlastimil Babka

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=20150930081304.GE12727@bbox \
    --to=minchan@kernel.org \
    --cc=ddstreet@ieee.org \
    --cc=gioh.kim@lge.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=vitalywool@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).