From: Samuel Ortiz <sameo@linux.intel.com>
To: Andrey Rusalin <arusalin@dev.rtsoft.ru>
Cc: michael.thalmeier@hale.at, linux-wireless@vger.kernel.org,
linux-nfc@lists.01.org
Subject: Re: [PATCH 0/3] NFC: pn533: fixes for i2c driver
Date: Sun, 2 Apr 2017 01:07:24 +0200 [thread overview]
Message-ID: <20170401230712.GJ22034@zurbaran.ger.intel.com> (raw)
In-Reply-To: <1482945059-12249-1-git-send-email-arusalin@dev.rtsoft.ru>
Hi Andrey,
On Wed, Dec 28, 2016 at 08:10:56PM +0300, Andrey Rusalin wrote:
> Each of these patches fix some oops that I met during
> tests of the driver with itead pn532 nfc module.
>
> First and third patches related to order of initialization driver,
> where interrupt handler was registered before work queues
> were ready to handle it.
> Also iqr was freed already after work queues were deinitialized.
>
> Second patch originally sent by Michael Thalmeier.
> I reworked a little bit to make it more readable.
>
> Andrey Rusalin (3):
> NFC: pn533: change order of free_irq and dev unregistration
> NFC: pn533: improve cmd queue handling
> NFC: pn533: change order operations in dev registation
All 3 patches applied, thanks.
Cheers,
Samuel.
prev parent reply other threads:[~2017-04-01 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 17:10 [PATCH 0/3] NFC: pn533: fixes for i2c driver Andrey Rusalin
2016-12-28 17:10 ` [PATCH 1/3] NFC: pn533: change order of free_irq and dev unregistration Andrey Rusalin
2016-12-28 17:10 ` [PATCH 2/3] NFC: pn533: improve cmd queue handling Andrey Rusalin
2016-12-28 17:10 ` [PATCH 3/3] NFC: pn533: change order operations in dev registation Andrey Rusalin
2017-04-01 23:07 ` Samuel Ortiz [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=20170401230712.GJ22034@zurbaran.ger.intel.com \
--to=sameo@linux.intel.com \
--cc=arusalin@dev.rtsoft.ru \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michael.thalmeier@hale.at \
/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).