From: mohit89mlnc@gmail.com (mohit verma)
To: kernelnewbies@lists.kernelnewbies.org
Subject: nameidata data structure again
Date: Thu, 6 Jan 2011 17:10:16 +0530 [thread overview]
Message-ID: <AANLkTi=YDNHY8zzEoaaKx+cAoJGj0DG3nqm5AKD_ehD5@mail.gmail.com> (raw)
hi folks,
we have qstr data structure part in nameidata structure in name resolution.
so it may work like this :
nameidata->path->dentry->qstr.
it is the real name component in a path name for that directory ro file (i
think so).
so what is the need of having another qstr like:
namidata->qstr (ie. last)
in nameidata structure.
sorry ,it may seem foolish to u guys but i ............
thanks in advance.
--
........................
*MOHIT VERMA*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110106/6f29d12c/attachment.html
next reply other threads:[~2011-01-06 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 11:40 mohit verma [this message]
2011-01-06 11:48 ` Fwd: nameidata data structure again mohit verma
2011-01-06 12:40 ` Rajat Sharma
2011-01-06 17:42 ` mohit verma
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='AANLkTi=YDNHY8zzEoaaKx+cAoJGj0DG3nqm5AKD_ehD5@mail.gmail.com' \
--to=mohit89mlnc@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).