mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: reiser@namesys.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: truncate_inode_pages_range patch to mainline ?
Date: Fri, 11 Nov 2005 11:10:43 -0800	[thread overview]
Message-ID: <1131736243.25354.53.camel@localhost.localdomain> (raw)
In-Reply-To: <20051111110535.1a491b87.akpm@osdl.org>

On Fri, 2005-11-11 at 11:05 -0800, Andrew Morton wrote:
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
> >
> > Hi Andrew,
> > 
> > I would like to find out, what your plans and/or concerns
> > to push
> > 
> > 	reiser4-truncate_inode_pages_range.patch
> > 
> > from your -mm tree to mainline ?
> 
> Well that's part of the reiser4 patch series.  It can be fed forward if we
> need it, of course.

Please do - if you don't have concerns with it.

> 
> > I need this for my madvise(REMOVE) work.
> 
> That's OK.
> 
> > And also, I see that 
> > madvise(REMOVE) is not in -mm2 also. Do you still
> > have concerns with it ?
> 
> I haven't looked much at the latest version yet, sorry.  The
> two-weeks-after-release window isn't a good time to be looking at new
> features, so there's quite a lot of material saved up for the
> six-week-interregnum.

There is no changes in the last version, except 1 page changelog
to include the discussions & future plans.

I am okay, as long as I am in the queue for next release. I was
hoping to get more testing in your -mm tree, in the meanwhile.

> 
> But yes, your patch still sucks ;)

I know :) 

Any suggestion on making it less sucky ? I really need this :(

Thanks,
Badari


      reply	other threads:[~2005-11-11 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11 18:50 Badari Pulavarty
2005-11-11 19:05 ` Andrew Morton
2005-11-11 19:10   ` Badari Pulavarty [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=1131736243.25354.53.camel@localhost.localdomain \
    --to=pbadari@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.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

Powered by JetHome