From: Niraj Kulkarni <kulkarniniraj14@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Get NFTLrecord reference from mtd_blktrans_dev argument
Date: Mon, 02 May 2011 11:23:33 +0530 [thread overview]
Message-ID: <4DBE46DD.60406@gmail.com> (raw)
Hi all,
I've observed that in kernel 2.6.38 (and maybe in previous
versions), in mtd_blktrans_ops callbacks provided by NFTL (nftlcore.c),
reference to NFTLrecord struct is obtained by just typecasting given
mtd_blktrans_dev. Though it works well, it highly position dependent
method and may break for mtd_blktrans_dev struct change. Given that
blktrans_dev struct already have a private field (void *priv) and it is
uninitialized in nftl, is it ok to write a trivial patch to assign
NFTLrecord pointer to mtd_blktrans_dev->priv?
Niraj
reply other threads:[~2011-05-02 5:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DBE46DD.60406@gmail.com \
--to=kulkarniniraj14@gmail.com \
--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 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.