From: Lars-Peter Clausen <lars@metafoo.de>
To: Hartmut Knaack <knaack.h@gmx.de>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: [RFC]coding style for NULL pointer checks
Date: Thu, 20 Feb 2014 10:04:39 +0100 [thread overview]
Message-ID: <5305C527.5060800@metafoo.de> (raw)
In-Reply-To: <53053609.40806@gmx.de>
On 02/19/2014 11:54 PM, Hartmut Knaack wrote:
[...]
> Concerning the staging drivers, I miss some motivation to work on device drivers that I don't have the devices for. Therefor I was mainly focusing on the ad799x. So, by the way, which are currently the show-stoppers for the ad799x preventing a move out of staging?
[...]
No, that was the last blocker, I do have a patch that moves it out of
staging, will submit it soon.
- Lars
next prev parent reply other threads:[~2014-02-20 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 12:19 [RFC]coding style for NULL pointer checks Hartmut Knaack
2014-02-16 18:56 ` Lars-Peter Clausen
2014-02-18 8:40 ` Jonathan Cameron
2014-02-19 22:54 ` Hartmut Knaack
2014-02-20 9:04 ` Lars-Peter Clausen [this message]
2014-02-20 18:55 ` Jonathan Cameron
2014-02-20 19:13 ` Lars-Peter Clausen
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=5305C527.5060800@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=linux-iio@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).