From: Artem Bityutskiy <dedekind1@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org
Subject: Re: linux-next: Tree for Feb 2 (fs/jffs2)
Date: Fri, 03 Feb 2012 07:37:35 +0200 [thread overview]
Message-ID: <1328247455.6750.25.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4F2AD4DE.7040508@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
On Thu, 2012-02-02 at 10:24 -0800, Randy Dunlap wrote:
> On 02/01/2012 07:45 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20120201:
>
>
> fs/jffs2/*.c still contains uses of ->read etc. instead of using
> mtd_read() etc.
The fix from Brian has been pushed to l2-mtd.git, should be fixed.
Thanks for reporting and sorry for the breakage.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org
Subject: Re: linux-next: Tree for Feb 2 (fs/jffs2)
Date: Fri, 03 Feb 2012 07:37:35 +0200 [thread overview]
Message-ID: <1328247455.6750.25.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4F2AD4DE.7040508@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
On Thu, 2012-02-02 at 10:24 -0800, Randy Dunlap wrote:
> On 02/01/2012 07:45 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20120201:
>
>
> fs/jffs2/*.c still contains uses of ->read etc. instead of using
> mtd_read() etc.
The fix from Brian has been pushed to l2-mtd.git, should be fixed.
Thanks for reporting and sorry for the breakage.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-03 5:37 UTC|newest]
Thread overview: 24+ 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 17:20 ` Manjunatha Halli
2012-02-02 18:40 ` [PATCH] " Randy Dunlap
2012-02-02 18:20 ` Manjunatha Halli
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: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 18:24 ` Randy Dunlap
2012-02-02 23:44 ` Stephen Rothwell
2012-02-02 23:44 ` Stephen Rothwell
2012-02-03 0:41 ` Brian Norris
2012-02-03 0:41 ` Brian Norris
2012-02-03 5:37 ` Artem Bityutskiy [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=1328247455.6750.25.camel@sauron.fi.intel.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.