From: Dan Streetman <ddstreet@ieee.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>
Subject: Re: [PATCH] MAINTAINERS: add zpool
Date: Wed, 3 Jun 2015 08:55:05 -0400 [thread overview]
Message-ID: <CALZtOND5TgiFgA-j7igmuiCx+MZN9d08BshQYiwPqpQTiXiqXg@mail.gmail.com> (raw)
In-Reply-To: <20150603035608.GA1652@swordfish>
On Tue, Jun 2, 2015 at 11:56 PM, Sergey Senozhatsky
<sergey.senozhatsky.work@gmail.com> wrote:
> On (06/02/15 14:30), Joe Perches wrote:
>> > >> +ZPOOL COMPRESSED PAGE STORAGE API
>> > >> +M: Dan Streetman <ddstreet@ieee.org>
>> > >> +L: linux-mm@kvack.org
>> > >> +S: Maintained
>> > >> +F: mm/zpool.c
>> > >> +F: include/linux/zpool.h
>> > >
>> > > If zpool.h is only included from files in mm/,
>> > > maybe zpool.h should be moved to mm/ ?
>> >
>> > It *could* be included by others, e.g. drivers/block/zram.
>> >
>> > It currently is only used by zswap though, so yeah it could be moved
>> > to mm/. Should I move it there, until (if ever) anyone outside of mm/
>> > wants to use it?
>>
>> Up to you.
>>
>> I think include/linux is a bit overstuffed and
>> whatever can be include local should be.
>>
>
> Hi,
>
> I agree, can be local for now. if zram will ever want to use zpool
> then we will move zpool.h to include/linux. just my 5 cents.
Ok. I'll send a patch to move it from include/linux to mm/ and update
the drivers there that include it.
>
> -ss
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-06-03 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 16:56 Dan Streetman
2015-06-02 21:09 ` Joe Perches
2015-06-02 21:19 ` Dan Streetman
2015-06-02 21:30 ` Joe Perches
2015-06-03 3:56 ` Sergey Senozhatsky
2015-06-03 12:55 ` Dan Streetman [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=CALZtOND5TgiFgA-j7igmuiCx+MZN9d08BshQYiwPqpQTiXiqXg@mail.gmail.com \
--to=ddstreet@ieee.org \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@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