From: Stephen Rothwell <sfr@canb.auug.org.au>
To: dedekind1@gmail.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: mtd api rework
Date: Tue, 31 Jan 2012 16:16:08 +1100 [thread overview]
Message-ID: <20120131161608.42c145d8f3f89dd3181cdac5@canb.auug.org.au> (raw)
In-Reply-To: <1327933829.13286.6.camel@sauron.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
Hi Artem,
On Mon, 30 Jan 2012 16:30:29 +0200 Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> we are doing MTD API rework and I've just pushed this patch to my l2-mtd
> tree:
>
> http://git.infradead.org/users/dedekind/l2-mtd.git/commit/a088d81808f6803ca6bfb9ea9148beef53fde1d2
>
> Which renames MTD function pointers to make sure no one uses them
> directly. I've build-tested this for i386 and arm and it compiles.
>
> However, there may be compile issues in future if one of subsystems not
> aware of the change try to use old names. Please, be aware. The right
> thing to do in this case for the subsystem is to either not use the
> pointer directly and use the corresponding mtd_func() wrapper. Please,
> let me know if there are any issues related to this change.
Thanks for the heads up. It seems OK so far, but you may want to check
the build results at http://kisskb.ellerman.id.au/linux-next as they
become available.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-31 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 14:30 mtd api rework Artem Bityutskiy
2012-01-31 5:16 ` Stephen Rothwell [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=20120131161608.42c145d8f3f89dd3181cdac5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dedekind1@gmail.com \
--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).