From: Mark Greer <mgreer@animalcreek.com>
To: Geoff Lansberry <geoff@kuvee.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Justin Bronder <justin@kuvee.com>
Subject: Re: [Patch] NFC: trf7970a:
Date: Wed, 14 Dec 2016 08:57:43 -0700 [thread overview]
Message-ID: <20161214155743.GA22282@animalcreek.com> (raw)
In-Reply-To: <CAO7Z3WJwf80mCqubSYTeK=BHN9sd=mzmL9th4Su-E25de6TmAg@mail.gmail.com>
On Tue, Dec 13, 2016 at 08:50:04PM -0500, Geoff Lansberry wrote:
> Hi Mark - Thanks for getting back to me. It's funny that you ask,
> because we are currently chasing a segfault that is happening in neard, but
> may end up back in the trf7970a driver. Have you ever heard on anyone
> having segfault problems related to the trf7970a hardware drivers?
No. Mind sharing more info on that segfault?
> I'll get you an update later tonight or tomorrow.
Okay, thanks.
Mark
--
next prev parent reply other threads:[~2016-12-14 16:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 19:48 [Patch] NFC: trf7970a: Geoff Lansberry
2016-04-18 19:48 ` [PATCH 1/4] NFC: trf7970a: Add support for gpio as SS Geoff Lansberry
2016-04-19 0:07 ` Julian Calaby
[not found] ` <CAO7Z3WJofeT4agChaZ-NQ5TwrMygdGRhG7myJkNuEb9i_g-Y=A@mail.gmail.com>
2016-04-20 1:24 ` Geoffrey Lansberry
2016-04-18 19:48 ` [PATCH 2/4] NFC: trf7970a: add TI recommended write of zero to Register 0x18 Geoff Lansberry
2016-04-18 19:48 ` [PATCH 3/4] NFC: trf7970a: add device tree option for 27MHz clock Geoff Lansberry
2016-04-19 0:11 ` Julian Calaby
2016-04-18 19:48 ` [PATCH 4/4] NFC: trf7970a: Add device tree option of 1.8 Volt IO voltage Geoff Lansberry
2016-04-19 0:12 ` Julian Calaby
2016-04-22 0:01 ` [Patch] NFC: trf7970a: Mark Greer
2016-12-13 22:05 ` Mark Greer
[not found] ` <CAO7Z3WJwf80mCqubSYTeK=BHN9sd=mzmL9th4Su-E25de6TmAg@mail.gmail.com>
2016-12-14 15:57 ` Mark Greer [this message]
2016-12-14 16:17 ` Geoff Lansberry
2016-12-14 17:10 ` Mark Greer
2016-12-14 18:35 ` Geoff Lansberry
2016-12-14 22:31 ` Mark Greer
2016-12-16 4:52 ` Mark Greer
2016-12-16 20:35 ` Mark Greer
2016-12-17 21:19 ` Geoff Lansberry
2016-12-19 3:07 ` Mark Greer
2017-02-08 22:53 ` Mark Greer
2017-02-08 22:56 ` Mark Greer
2017-02-09 15:54 ` Geoff Lansberry
2017-02-09 21:27 ` Mark Greer
2017-02-10 0:41 ` Geoff Lansberry
2017-02-10 4:20 ` Mark Greer
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=20161214155743.GA22282@animalcreek.com \
--to=mgreer@animalcreek.com \
--cc=aloisio.almeida@openbossa.org \
--cc=geoff@kuvee.com \
--cc=justin@kuvee.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sameo@linux.intel.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).