From: nick <xerofoify@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: MTD Maling List <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Cannot find jffs2_commit_write
Date: Tue, 16 Dec 2014 12:18:28 -0500 [thread overview]
Message-ID: <54906964.9020309@gmail.com> (raw)
In-Reply-To: <CAMuHMdU1DQBcq5AiVYaT8m3b7x_HFa6SMy-KOw5m7W=S8LPrJw@mail.gmail.com>
Thanks Geert,
I am wondering then why do we still have this message in the TODO file for jffs2,
- disable compression in commit_write()?. If anyone can explain why this is still
needed I will gladly look into it, otherwise I am sending a patch to remove this
TODO for jffs2.
Regards Nick
P.S. I do am linus's tree cloned, I am using lxr only for searching the recent tree.
On 2014-12-16 05:57 AM, Geert Uytterhoeven wrote:
> Hi Nick,
>
> On Mon, Dec 15, 2014 at 5:12 PM, nick <xerofoify@gmail.com> wrote:
>> I seem to not be able to locate jffs2_commit_write by searching with lxr. If someone can tell me what file the function is located in that would be greatly appreciated.
>
> That's because it does not exist. Presumably someone forgot to update
> an error message when it was renamed (before it entered mainline in ... 2002!
>
> BTW, please clone Linus' git tree instead of lurking in lxr for real development
> (I assume that's what you want to do? ;-)
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
prev parent reply other threads:[~2014-12-16 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 16:12 Cannot find jffs2_commit_write nick
2014-12-16 10:57 ` Geert Uytterhoeven
2014-12-16 17:18 ` nick [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=54906964.9020309@gmail.com \
--to=xerofoify@gmail.com \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).