From: Namhyung Kim <namhyung@gmail.com>
To: Balachandar <bala1486@gmail.com>
Cc: kernelnewbies@nl.linux.org, linux-c-programming@vger.kernel.org
Subject: Re: Use of double pointer in linux kernel Hash list implementation
Date: Fri, 18 Jun 2010 11:10:03 +0900 [thread overview]
Message-ID: <1276827003.1746.24.camel@leonhard> (raw)
In-Reply-To: <AANLkTinj8yacrvasccTNM9CtF9pny0U3QX47wtRT-Abq@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
2010-06-17 (목), 10:34 -0400, Balachandar:
>
> My doubt is why not use *prev as it is used in list_head
> implementation rather than **pprev.
hlist is simple linked list so there is no need of *prev. **pprev is a
kind of hack and should not be accessed in the outside of hlist. If you
need *prev, just use list_head.
--
Regards,
Namhyung Kim
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-06-18 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 2:50 Use of double pointer in linux kernel Hash list implementation Balachandar
2010-06-17 3:32 ` Namhyung Kim
2010-06-17 14:34 ` Balachandar
2010-06-18 2:10 ` Namhyung Kim [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=1276827003.1746.24.camel@leonhard \
--to=namhyung@gmail.com \
--cc=bala1486@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-c-programming@vger.kernel.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).