linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
	linux-mtd@lists.infradead.org,
	Randy Dunlap <rdunlap@xenotime.net>,
	linux-next@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 2 (fs/jffs2)
Date: Thu, 2 Feb 2012 16:41:47 -0800	[thread overview]
Message-ID: <CAN8TOE9tPypqedF4HUnNPLO9pXbKig3oij6qO6BnytACGTWGwQ@mail.gmail.com> (raw)
In-Reply-To: <20120203104453.8438182da9f365c24d3c2128@canb.auug.org.au>

On Thu, Feb 2, 2012 at 3:44 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Thu, 02 Feb 2012 10:24:30 -0800 Randy Dunlap <rdunlap@xenotime.net> wrote:
>>
>> fs/jffs2/*.c still contains uses of ->read etc. instead of using
>> mtd_read() etc.
>>
>> fs/jffs2/read.c:36:8: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/read.c:112:8: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/nodemgmt.c:669:8: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/readinode.c:83:9: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/readinode.c:676:9: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/readinode.c:954:8: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/readinode.c:1040:9: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/readinode.c:1216:8: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/readinode.c:1275:10: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/scan.c:286:8: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/gc.c:590:8: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/gc.c:894:10: error: 'struct mtd_info' has no member named 'read'
>> fs/jffs2/gc.c:977:9: error: 'struct mtd_info' has no member named 'read'
>
> They were probably missed because they use the jffs2_flash_read() macro
> in fs/jffs2/os-linux.h

I just sent a patch that fixes this, FYI. If Artem and Randy ACK it,
it'll probably go into l2-mtd-2.6.git.

Brian

  reply	other threads:[~2012-02-03  0:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02  3:45 linux-next: Tree for Feb 2 Stephen Rothwell
2012-02-02 18:07 ` linux-next: Tree for Feb 2 (media/radio/wl128x) Randy Dunlap
2012-02-02 17:20   ` Manjunatha Halli
2012-02-02 18:40     ` [PATCH] " Randy Dunlap
2012-02-02 18:20       ` Manjunatha Halli
2012-02-05 20:32         ` Randy Dunlap
2012-02-02 18:10 ` linux-next: Tree for Feb 2 (trace/events/sunrpc.h) Randy Dunlap
2012-02-09  2:37   ` Steven Rostedt
2012-02-09  3:14     ` Myklebust, Trond
2012-02-09  3:30       ` Steven Rostedt
2012-02-09 16:14       ` Randy Dunlap
2012-02-02 18:24 ` linux-next: Tree for Feb 2 (fs/jffs2) Randy Dunlap
2012-02-02 23:44   ` Stephen Rothwell
2012-02-03  0:41     ` Brian Norris [this message]
2012-02-03  5:37   ` Artem Bityutskiy
2012-02-02 23:28 ` linux-next: Tree for Feb 2 (kvmtool) Randy Dunlap
2012-03-27 10:19   ` Pekka Enberg

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=CAN8TOE9tPypqedF4HUnNPLO9pXbKig3oij6qO6BnytACGTWGwQ@mail.gmail.com \
    --to=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /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).