NFC: Don't handle consequent RSET frames after UA
authorWaldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
Fri, 21 Sep 2012 12:02:46 +0000 (14:02 +0200)
committerSamuel Ortiz <sameo@linux.intel.com>
Mon, 24 Sep 2012 22:17:27 +0000 (00:17 +0200)
commit12bfd1e8906637757a0bc42970f0fc11a9918019
treebd72d458f4083227ed0fd237fcfed30d06ab866a
parent9010e39f508ee57dc9a7675073659cb9d019a802
NFC: Don't handle consequent RSET frames after UA

During processing incoming RSET frame chip, possibly due to
its internal timout, can retrnasmit an another RSET which
is next queued for processing in shdlc layer.

In case when we accept processed RSET skip those remaining on
the rcv queue until chip will send it's first S or I frame.
This will mean the chip completed connection as well.

Signed-off-by: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
net/nfc/hci/llc_shdlc.c