From: Karel Zak <kzak@redhat.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
Timofey Titovets <nefelim4ag@gmail.com>,
util-linux@vger.kernel.org
Subject: Re: [RFC] Zram handle util
Date: Mon, 21 Jul 2014 10:10:03 +0200 [thread overview]
Message-ID: <20140721081003.GC17373@x2.net.home> (raw)
In-Reply-To: <20140721075721.GC8180@gmail.com>
On Mon, Jul 21, 2014 at 07:57:21AM +0000, Minchan Kim wrote:
> First of all, Thanks for your effor, Timofey!
>
> Adding such userspace tool in kernel src directory doesn't make sense.
> If we wanted it, there are tons of user tools in kernel src directory
> so IMHO, util-linux is better place.
I don't think that regular (non-debugging, non-development) userspace utils
belong to the kernel tree...
Please, see the howtos recommended by Sami and send a patch(es) with
the code and a man page. It (util-linux specific details) does not
have to be perfect, the important is to have correctly implemented
zram specific things.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-07-21 8:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 17:28 [RFC] Zram handle util Timofey Titovets
2014-07-19 19:12 ` Sami Kerola
[not found] ` <CAGqmi765JkidXDpi6bP2qUk5U7Xry5nF7y0WY4Y6M_Fq8Eiqeg@mail.gmail.com>
2014-07-19 22:44 ` Fwd: " Timofey Titovets
2014-07-20 9:38 ` Timofey Titovets
2014-07-20 20:36 ` Davidlohr Bueso
2014-07-21 7:57 ` Minchan Kim
2014-07-21 8:10 ` Karel Zak [this message]
2014-07-23 17:28 ` [RFC] [Patch] Created zramctl Timofey Titovets
2014-07-23 17:43 ` Dave Reisner
2014-07-23 17:51 ` Timofey Titovets
2014-07-24 7:29 ` Karel Zak
2014-07-24 7:26 ` Karel Zak
2014-07-24 10:23 ` Benno Schulenberg
2014-07-27 19:04 ` [RFC] [Patch v2] " Timofey Titovets
2014-08-01 10:37 ` Karel Zak
2014-08-02 14:22 ` Timofey Titovets
-- strict thread matches above, loose matches on Subject: below --
2014-07-20 14:45 [RFC] Zram handle util Timofey Titovets
2014-07-20 15:42 ` Sami Kerola
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=20140721081003.GC17373@x2.net.home \
--to=kzak@redhat.com \
--cc=davidlohr@hp.com \
--cc=minchan@kernel.org \
--cc=nefelim4ag@gmail.com \
--cc=util-linux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.