public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Ivan Chan <ivanming@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: how to implement prepare_write, commit_write for ubifs
Date: Wed, 17 Jun 2009 11:29:24 +0300	[thread overview]
Message-ID: <1245227364.9487.7.camel@localhost.localdomain> (raw)
In-Reply-To: <d16af8a00906170053p11a4f0e3vd0bbef99d65b9aac@mail.gmail.com>

On Wed, 2009-06-17 at 15:53 +0800, Ivan Chan wrote:
> Hi all,
> 
> I am porting UBIFS/UBI to 2.6.4 kernel, however, 2.6.4 kernel requires
> prepare_write, commit_write in address_space_operations (defined in
> include/linux/fs.h),
> but it is no longer exists in 2.6.2x kernel.
> 
> How can I rewrite these function for 2.6.4 kernel?
> 
> In 2.6.2x, there is similar function write_begin, and write_end, but
> the API requires
> struct address_space *mapping,  struct page **pagep, void **fsdata,
> 
> Is that possible and how to provide this argument in 2.6.4 kernel?

ATM we support UBIFS back-ports from v2.6.24 to v2.6.30.

The change of the address space operation happened between 2.6.23 and
2.6.24.

In the paste, we also supported UBIFS back-ports for kerneld
2.6.21-2.6.23. But then we dropped them because it became increasingly
difficult to back-port stuff there.

So what would suggest you do is:

a). Start with the old and unsupported 2.6.23 UBIFS back-port which you
may find here: git://git.infradead.org/users/dedekind/ubifs-v2.6.23.git

b). Back-port this UBIFS 2.6.23 stuff to your ancient 2.6.4, it should
be easier to do comparing to back-porting the newest stuff.

c). Back port the rest of the UBIFS changes/fixes from the latest
kernels, e.g., from the UBIFS 2.6.30 back-port.

The back-ports URLS may be found here:
http://www.linux-mtd.infradead.org/doc/ubifs.html#L_source

Or just see here:
http://git.infradead.org/

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-06-17  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  7:53 how to implement prepare_write, commit_write for ubifs Ivan Chan
2009-06-17  8:29 ` Artem Bityutskiy [this message]
2009-06-17 12:24   ` Ivan

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=1245227364.9487.7.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=ivanming@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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