From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Staging clear up
Date: Thu, 10 Nov 2011 09:49:04 +0000 [thread overview]
Message-ID: <20111110094904.GA29635@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1320858754.32205.1110.camel@vkoul-udesk3>
On Wed, Nov 09, 2011 at 10:42:34PM +0530, Vinod Koul wrote:
> On Wed, 2011-11-09 at 17:08 +0000, Mark Brown wrote:
> > On Wed, Nov 09, 2011 at 10:33:01PM +0530, Vinod Koul wrote:
> >
> > > Offtopic: I am ready with v2 of compressed API, testing stuff out. If
> > > you/Dimitris have stuff to add, please drop me a note. I didn't see any
> > > update after I published the tree
> >
> > I'm pretty sure Dimitris has some stuff.
> Care to send me?
>
> I will push my updates worst case by week end. Fixed some usual misses
> found in testing and reworked the avail calculation.
Hi Vinod,
Will send some of my updates when I re-work them. At the moment I was
working around some of the issues I found.
Thanks,
Dimitris
next prev parent reply other threads:[~2011-11-10 9:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 21:16 Staging clear up Alan Cox
2011-11-08 21:48 ` Greg KH
2011-11-08 23:51 ` Alan Cox
2011-11-09 0:05 ` Greg KH
2011-11-09 12:13 ` Mark Brown
2011-11-09 16:00 ` Vinod Koul
2011-11-09 16:42 ` Mark Brown
2011-11-09 16:47 ` Vinod Koul
2011-11-09 16:53 ` Mark Brown
2011-11-09 17:03 ` Vinod Koul
2011-11-09 17:08 ` Mark Brown
2011-11-09 17:12 ` Vinod Koul
2011-11-10 9:49 ` Dimitris Papastamos [this message]
2011-11-09 16:55 ` Greg KH
2011-11-09 16:58 ` Mark Brown
2011-11-09 17:30 ` Alan Cox
2011-11-09 22:59 ` Mark Brown
2011-11-09 23:03 ` Alan Cox
2011-11-09 23:03 ` Mark Brown
2011-11-09 23:05 ` Alan Cox
2011-11-09 23:11 ` Mark Brown
2011-11-09 23:25 ` Alan Cox
2011-11-10 2:52 ` Vinod Koul
2011-11-10 8:54 ` Alan Cox
2011-11-27 1:30 ` Greg KH
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=20111110094904.GA29635@opensource.wolfsonmicro.com \
--to=dp@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.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 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.