From: Alexander Riesen <alexander.riesen@cetitec.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org,
Josh Triplett <josh@freedesktop.org>,
Christopher Li <sparse@chrisli.org>
Subject: Re: Why sparse does not support context tracking?
Date: Mon, 04 May 2015 16:05:59 +0200 [thread overview]
Message-ID: <55477CC7.4020807@cetitec.com> (raw)
In-Reply-To: <1430746737.2013.22.camel@sipsolutions.net>
On 05/04/2015 03:38 PM, Johannes Berg wrote:
> On Mon, 2015-05-04 at 13:05 +0200, Alexander Riesen wrote:
>>
>> Revert the context tracking code
>>
>> So it seems that the code has problems with different contexts. Still, it seems
>> a bit heavy-handed to remove it completely (assuming it worked, of course).
>
> It didn't really work. It had a lot of issues that were too big for my
> little wireless-focused brain :)
Ah, pity. Wasn't there any hope for it?
prev parent reply other threads:[~2015-05-04 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 11:05 Why sparse does not support context tracking? Alexander Riesen
2015-05-04 13:38 ` Johannes Berg
2015-05-04 14:05 ` Alexander Riesen [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=55477CC7.4020807@cetitec.com \
--to=alexander.riesen@cetitec.com \
--cc=johannes@sipsolutions.net \
--cc=josh@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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.