From: "Darren Jenkins" <darrenrjenkins@gmail.com>
To: Marko Kreen <markokr@gmail.com>
Cc: Philipp Reisner <philipp.reisner@linbit.com>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH] The require_context attribute
Date: Wed, 2 Apr 2008 19:13:40 +1100 [thread overview]
Message-ID: <82faac5b0804020113j762da44bjff07f8f529e802fb@mail.gmail.com> (raw)
In-Reply-To: <e51f66da0804010710x13711acdy8862b5632db94012@mail.gmail.com>
On Wed, Apr 2, 2008 at 1:10 AM, Marko Kreen <markokr@gmail.com> wrote:
>
> You take an address, how can it be NULL?
>
Yep, this could only happen if both the pointer was NULL and ctype was
the first structure member of struct symbol.
However neither of these things are true here.
prev parent reply other threads:[~2008-04-02 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 12:00 [PATCH] The require_context attribute Philipp Reisner
2008-04-01 10:07 ` Darren Jenkins
2008-04-01 14:00 ` Philipp Reisner
2008-04-01 14:10 ` Marko Kreen
2008-04-01 14:41 ` Philipp Reisner
2008-04-02 8:13 ` Darren Jenkins [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=82faac5b0804020113j762da44bjff07f8f529e802fb@mail.gmail.com \
--to=darrenrjenkins@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=markokr@gmail.com \
--cc=philipp.reisner@linbit.com \
/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).