From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
devel@linuxdriverproject.org, rcj@linux.vnet.ibm.com,
sjenning@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Various cleanups/fixes to zcache (v3).
Date: Thu, 14 Feb 2013 17:57:40 -0500 [thread overview]
Message-ID: <20130214225740.GA8104@phenom.dumpdata.com> (raw)
In-Reply-To: <20130214172926.GA17343@kroah.com>
On Thu, Feb 14, 2013 at 09:29:26AM -0800, Greg KH wrote:
> On Thu, Feb 14, 2013 at 09:02:47AM -0800, Dan Magenheimer wrote:
> > > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > > Subject: Re: [PATCH] Various cleanups/fixes to zcache (v3).
> > >
> > > On Thu, Feb 14, 2013 at 08:56:01AM -0800, Dan Magenheimer wrote:
> > > > > From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
> > > > > Subject: [PATCH] Various cleanups/fixes to zcache (v3).
> > > > >
> > > > > From Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> # This line is ignored.
> > > > > From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > > > > Subject: [PATCH] Various cleanups/fixes to zcache (v3).
> > > > > In-Reply-To:
> > > > >
> > > > > Hey Greg,
> > > > >
> > > > > These patches do various cleanups of the zcache driver. The majority of the
> > > > > work is just to move all the different counters out to a debug file. The next
> > > > > step would be to figure out which ones are actually pertient and which can
> > > > > go under the knife. Oh, and also fix some of the compiler warnings.
> > > > >
> > > > > This is based on top of ommit 76426daf50d5df38893cc189e9ccd026093debc8
> > > > > ("staging/zcache: Fix/improve zcache writeback code, tie to a config option")
> > > > > so should apply cleanly to your tree.
> > > > >
> > > > > Please apply.
> > > >
> > > > Useful cleanups.
> > > >
> > > > Hopefully not too late for 3.9-rc0.
> > >
> > > You all did see my "the staging tree is closed except for bugfixes for
> > > 3.9" message last week, right?
> >
> > Oops, sorry, no I missed that.
> >
> > > Sorry, this will have to wait for 3.10.
> >
> > No problem, no bugs fixed here, though I expect we'll see
> > the same complaints posted again about the compiler warnings.
>
> Then why not just redo that one patch, and send it to me, and then
> rebase all of the other patches on top of it? That way I can accept the
> "fix the complier warnings" patch now, and the rest can wait.
Aye aye captain. Going to send them tomorrow (zbud/zcache).
next prev parent reply other threads:[~2013-02-14 22:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1360811106-2679-1-git-send-email-konrad.wilk@oracle.com>
2013-02-14 16:56 ` [PATCH] Various cleanups/fixes to zcache (v3) Dan Magenheimer
2013-02-14 16:59 ` Greg KH
2013-02-14 17:02 ` Dan Magenheimer
2013-02-14 17:29 ` Greg KH
2013-02-14 22:57 ` Konrad Rzeszutek Wilk [this message]
2013-02-15 17:53 ` [PATCH] Compile bug-fixes to zcache (v4) Konrad Rzeszutek Wilk
2013-02-15 17:53 ` [PATCH 1/4] zcache: Fix compile warnings due to usage of debugfs_create_size_t Konrad Rzeszutek Wilk
2013-02-15 17:53 ` [PATCH 2/4] ramster: " Konrad Rzeszutek Wilk
2013-02-15 17:53 ` [PATCH 3/4] zbud: " Konrad Rzeszutek Wilk
2013-02-15 17:53 ` [PATCH 4/4] zcache/zbud: Fix __init mismatch Konrad Rzeszutek Wilk
2013-02-15 18:17 ` [PATCH] Compile bug-fixes to zcache (v4) Greg KH
2013-02-15 18:48 ` Konrad Rzeszutek Wilk
2013-02-15 18:53 ` Greg KH
2013-02-14 3:04 [PATCH] Various cleanups/fixes to zcache (v3) Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 01/16] zcache: s/int/bool/ on the various options Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 02/16] zcache: Provide accessory functions for counter increase Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 03/16] zcache: Provide accessory functions for counter decrease Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 04/16] zcache: The last of the atomic reads has now an accessory function Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 05/16] zcache: Fix compile warnings due to usage of debugfs_create_size_t Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 06/16] zcache: Make the debug code use pr_debug Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 07/16] zcache: Move debugfs code out of zcache-main.c file Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 08/16] zcache/debug: Use an array to initialize/use debugfs attributes Konrad Rzeszutek Wilk
2013-02-14 3:04 ` [PATCH 09/16] zcache: Move the last of the debugfs counters out Konrad Rzeszutek Wilk
2013-02-14 3:05 ` [PATCH 10/16] zcache: Module license is defined twice Konrad Rzeszutek Wilk
2013-02-14 3:05 ` [PATCH 11/16] zcache/debug: Coalesce all debug under CONFIG_ZCACHE_DEBUG Konrad Rzeszutek Wilk
2013-02-14 3:05 ` [PATCH 12/16] zcache/zbud: Fix compiler warnings Konrad Rzeszutek Wilk
2013-02-14 3:05 ` [PATCH 13/16] zcache/zbud: Add incremental accessory counters Konrad Rzeszutek Wilk
2013-02-14 3:05 ` [PATCH 14/16] zcache/zbud: Provide the accessory functions for counter decrease Konrad Rzeszutek Wilk
2013-02-14 3:05 ` [PATCH 15/16] ramster: Fix compile warnings due to usage of debugfs_create_size_t Konrad Rzeszutek Wilk
2013-02-14 3:05 ` [PATCH 16/16] zcache/zbud: Fix __init mismatch Konrad Rzeszutek Wilk
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=20130214225740.GA8104@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rcj@linux.vnet.ibm.com \
--cc=sjenning@linux.vnet.ibm.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