From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>, gopi.st@samsung.com
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
ngupta@vflare.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, v.narang@samsung.com,
pankaj.m@samsung.com, a.sahrawat@samsung.com,
prakash.a@samsung.com, himanshu.sh@samsung.com,
lalit.mohan@samsung.com
Subject: Re: [PATCH v2] zram: better utilization of zram swap space
Date: Fri, 29 Dec 2017 18:21:49 +0900 [thread overview]
Message-ID: <20171229092149.GA764@jagdpanzerIV> (raw)
In-Reply-To: <20171229072656.GA10366@bbox>
Hello,
On (12/29/17 16:26), Minchan Kim wrote:
[..]
> > Gopi Sai Teja, please discuss with Sergey about patch credit.
>
> Hi Gopi Sai Teja,
>
> Now I read previous thread at v1 carefully, I found Sergey already
> sent a patch long time ago which is almost same one I suggested.
> And he told he will send a patch soon so I want to wait his patch.
> We are approaching rc6 now so it's not urgent.
Thanks, Minchan.
Sorry for the noise and confusion. I was going to send it out some
time ago, but got interrupted.
> Sergey, sorry for missing your patch at that time.
> Could you resend your patch when you have a time? Please think
> over better name of the function "zs_get_huge_class_size_watermark"
sure, will take a look.
thanks,
-ss
prev parent reply other threads:[~2017-12-29 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171222103443epcas5p41f45e1a99146aac89edd63f76a3eb62a@epcas5p4.samsung.com>
2017-12-22 10:30 ` [PATCH v2] zram: better utilization of zram swap space Gopi Sai Teja
2017-12-27 6:29 ` Minchan Kim
2017-12-27 7:10 ` Sergey Senozhatsky
2017-12-28 0:00 ` Minchan Kim
2017-12-29 7:26 ` Minchan Kim
2017-12-29 9:21 ` 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=20171229092149.GA764@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=a.sahrawat@samsung.com \
--cc=gopi.st@samsung.com \
--cc=himanshu.sh@samsung.com \
--cc=lalit.mohan@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=pankaj.m@samsung.com \
--cc=prakash.a@samsung.com \
--cc=v.narang@samsung.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).