public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: Linux Filesystems <linux-fsdevel@vger.kernel.org>,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: 2.6.21-rc6 new aops patchset
Date: Fri, 13 Apr 2007 01:45:35 +0200	[thread overview]
Message-ID: <20070412234535.GE23523@wotan.suse.de> (raw)
In-Reply-To: <20070412172734.GO21982@ca-server1.us.oracle.com>

On Thu, Apr 12, 2007 at 10:27:34AM -0700, Mark Fasheh wrote:
> On Thu, Apr 12, 2007 at 06:48:52AM +0200, Nick Piggin wrote:
> > Need to think about how to merge this.
> 
> Maybe a spin in -mm? That'll have to be minus fs-ocfs2-aops.patch, but I'm
> just working out the last few issues in a new one for you anyway.

Yeah, I guess that's the best way. Hopefully there are no major clashes ;)

I'll ask Andrew to merge after 2.6.21 opens.


> FWIW, I'm
> very happy with the way these patches have gone so far.

Great, that's good to hear.


> Here's another trivial patch...

Yep, I think that's a reasonable export. Will apply.

> 	--Mark
> 
> --
> Mark Fasheh
> Senior Software Developer, Oracle
> mark.fasheh@oracle.com
> 
> 
> >From nobody Mon Sep 17 00:00:00 2001
> From: Mark Fasheh <mark.fasheh@oracle.com>
> Date: Thu, 12 Apr 2007 10:18:05 -0700
> Subject: [PATCH] Export page_zero_new_buffers()
> 
> Any file system that wants to implement their own ->write_end() will
> probably want this.
> 
> Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
> 
> ---
> 
>  fs/buffer.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> 86e3778a4acc27bd93e5885140f9e9fd1b967cf1
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 9aae38e..7559bc0 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -1889,6 +1889,7 @@ void page_zero_new_buffers(struct page *
>  		bh = bh->b_this_page;
>  	} while (bh != head);
>  }
> +EXPORT_SYMBOL(page_zero_new_buffers);
>  
>  static int __block_commit_write(struct inode *inode, struct page *page,
>  		unsigned from, unsigned to)
> -- 
> 1.3.3

  reply	other threads:[~2007-04-12 23:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12  4:48 2.6.21-rc6 new aops patchset Nick Piggin
2007-04-12 16:37 ` Badari Pulavarty
2007-04-12 23:25   ` Nick Piggin
2007-04-13 16:42     ` Badari Pulavarty
2007-04-14  0:52       ` Nick Piggin
2007-04-17 18:41         ` Badari Pulavarty
2007-04-18  5:04           ` Nick Piggin
2007-04-12 17:05 ` Miklos Szeredi
2007-04-12 23:41   ` Nick Piggin
2007-04-12 17:27 ` Mark Fasheh
2007-04-12 23:45   ` Nick Piggin [this message]
2007-04-17  0:19 ` Mark Fasheh
2007-04-17  5:59   ` Nick Piggin
2007-04-17  9:33     ` Christoph Hellwig
2007-04-17  9:47       ` Nick Piggin
2007-04-17  9:58         ` Christoph Hellwig
2007-04-17 11:18           ` Nick Piggin

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=20070412234535.GE23523@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --cc=miklos@szeredi.hu \
    /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