From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dan Magenheimer <dan.magenheimer@oracle•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Konrad Wilk <konrad.wilk@oracle•com>
Subject: Re: next phase of tmem into linux-next
Date: Thu, 2 Jun 2011 09:48:50 +1000 [thread overview]
Message-ID: <20110602094850.92063cbe.sfr@canb.auug.org.au> (raw)
In-Reply-To: <dedd3fa5-5dc3-4ce1-9ab4-dc77e23a6d7d@default>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
Hi Dan,
On Wed, 1 Jun 2011 09:22:59 -0700 (PDT) Dan Magenheimer <dan.magenheimer@oracle•com> wrote:
>
> OK, I see "Already up-to-date" in merge.log. I'll assume
> that the new frontswap commits will lag a day. (Thanks,
> Konrad, for helping me find this info and pointing out the
> probable lag.)
>
> (A thought... perhaps the merge.log generation script should
> do a "date" at the beginning and end, so one knows if one
> has just missed your merge window?)
Yeah, well I am out of sync (timezone-wise) with most people, so good
thought. Though I actually fetch all the trees before I starte merging
them, but it will give people some idea.
> > The tree is still called "cleancache" in linux-next. Should I change
> > that to something more generic?
>
> Yes please. A good short name would be "tmem", but if you want
> something longer and more descriptive maybe, "transcendent_memory".
> I expect in the future that this might be the path for, for
> example, tmem-related code that is promoted from drivers/staging.
> E.g., the generic tmem.c code in drivers/staging/zcache could
> probably end up in lib at some point if/when there are multiple users.
OK, I have renamed it to tmem (much easier to type :-)).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-06-01 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 0:49 next phase of tmem into linux-next Dan Magenheimer
2011-06-01 4:25 ` Stephen Rothwell
2011-06-01 16:22 ` Dan Magenheimer
2011-06-01 23:48 ` Stephen Rothwell [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=20110602094850.92063cbe.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dan.magenheimer@oracle$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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