From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Matthew L. Creech" <mlcreech@gmail.com>
Cc: Ben Gardiner <bengardiner@nanometrics.ca>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mkfs.ubifs: free-space-fixup: note supported kernels
Date: Thu, 19 May 2011 08:56:39 +0300 [thread overview]
Message-ID: <1305784599.2630.41.camel@localhost> (raw)
In-Reply-To: <BANLkTimTZOoU6z9xTKANk4sGLMCKaxmy8w@mail.gmail.com>
On Thu, 2011-05-19 at 01:41 -0400, Matthew L. Creech wrote:
> Thanks Ben, I missed Artem's reply asking for this.
>
> On Wed, May 18, 2011 at 4:57 PM, Ben Gardiner
> <bengardiner@nanometrics.ca> wrote:
> >
> > Note in the help text and comment that kernel release 2.6.39 is required
> > for the free space fixup to be performed.
> >
>
> Will it actually be included in 2.6.39? The flag exists there, but
> I'd assumed the code changes wouldn't be merged until the next cycle.
Hi, indeed, yes, I'm planning to merge this upstream, but in 2.6.40. I'm
sorry for misleading infromation.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-05-19 6:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 22:14 [PATCH v2] mkfs.ubifs: add "-F" option for "free-space fixup" Matthew L. Creech
2011-05-11 20:09 ` Ben Gardiner
2011-05-11 21:01 ` Matthew L. Creech
2011-05-11 21:02 ` [PATCH 1/1] " Matthew L. Creech
2011-05-12 13:13 ` Artem Bityutskiy
2011-05-18 20:57 ` [PATCH] mkfs.ubifs: free-space-fixup: note supported kernels Ben Gardiner
2011-05-19 5:41 ` Matthew L. Creech
2011-05-19 5:56 ` Artem Bityutskiy [this message]
2011-05-19 12:14 ` [PATCH v2] " Ben Gardiner
2011-05-20 10:15 ` Artem Bityutskiy
2011-05-24 14:36 ` Ben Gardiner
2011-05-20 10:11 ` [PATCH 1/1] mkfs.ubifs: add "-F" option for "free-space fixup" Artem Bityutskiy
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=1305784599.2630.41.camel@localhost \
--to=dedekind1@gmail.com \
--cc=bengardiner@nanometrics.ca \
--cc=linux-mtd@lists.infradead.org \
--cc=mlcreech@gmail.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;
as well as URLs for NNTP newsgroup(s).