<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/git/stable/linux.git/net/nfc/llcp/commands.c, branch master</title>
<subtitle>Linux kernel stable tree</subtitle>
<id>https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=master</id>
<link rel='self' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/'/>
<updated>2013-04-26T10:37:28+00:00</updated>
<entry>
<title>NFC: Move LLCP code to the NFC top level diirectory</title>
<updated>2013-04-26T10:37:28+00:00</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2013-04-26T09:49:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=30cc4587659e1c9b1bfade8b2a757d91e04758ab'/>
<id>urn:sha1:30cc4587659e1c9b1bfade8b2a757d91e04758ab</id>
<content type='text'>
And stop making it optional. LLCP is a fundamental part of the NFC
specifications and making it optional does not make much sense.

Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Use localy stored remote_miu value if not set at socket level</title>
<updated>2013-04-11T14:28:58+00:00</updated>
<author>
<name>Thierry Escande</name>
<email>thierry.escande@linux.intel.com</email>
</author>
<published>2013-04-02T08:25:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=66cbfa10f3bdbc86222598ac700c352da90e588f'/>
<id>urn:sha1:66cbfa10f3bdbc86222598ac700c352da90e588f</id>
<content type='text'>
If remote_miu value is not set in the socket (i.e. connection-less socket) the
value stored in the local is used.

Signed-off-by: Thierry Escande &lt;thierry.escande@linux.intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Fix zero octets length SDU handling</title>
<updated>2013-04-11T14:28:57+00:00</updated>
<author>
<name>Olivier Guiter</name>
<email>olivier.guiter@linux.intel.com</email>
</author>
<published>2013-03-25T10:24:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b23d666a8857e521384d0eec75a7362b80a39b8'/>
<id>urn:sha1:0b23d666a8857e521384d0eec75a7362b80a39b8</id>
<content type='text'>
LLCP Validation test #2 (Connection-less information transfer) send a
service data unit of zero octets length. This is now handled correctly.

Signed-off-by: Olivier Guiter &lt;olivier.guiter@linux.intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Socket miux is a big endian field</title>
<updated>2013-04-11T14:28:56+00:00</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2013-03-20T15:06:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5eef6669759f8e291ab0347894876b532c242324'/>
<id>urn:sha1:5eef6669759f8e291ab0347894876b532c242324</id>
<content type='text'>
The MIUX must be transmitted in big endian and as such we have to convert
it properly.

Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Add cleanup support for unreplied SNL requests</title>
<updated>2013-03-10T22:16:41+00:00</updated>
<author>
<name>Thierry Escande</name>
<email>thierry.escande@linux.intel.com</email>
</author>
<published>2013-03-04T14:43:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=40213fa8513c2a92e7390f25571f7c17c7955e2b'/>
<id>urn:sha1:40213fa8513c2a92e7390f25571f7c17c7955e2b</id>
<content type='text'>
If the remote LLC doesn't reply in time to our SNL requests we remove
them from the list of pending requests. The timeout is fixed to an
arbitrary value of 3 times remote_lto.

When not replied, the local LLC broadcasts NFC_EVENT_LLC_SDRES nl events for
the concerned uris with sap values set to LLCP_SDP_UNBOUND (which is 65).

Signed-off-by: Thierry Escande &lt;thierry.escande@linux.intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Service Name Lookup netlink interface</title>
<updated>2013-03-10T22:14:54+00:00</updated>
<author>
<name>Thierry Escande</name>
<email>thierry.escande@linux.intel.com</email>
</author>
<published>2013-02-15T09:43:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d9b8d8e19b073096d3609bbd60f82148d128b555'/>
<id>urn:sha1:d9b8d8e19b073096d3609bbd60f82148d128b555</id>
<content type='text'>
This adds a netlink interface for service name lookup support.
Multiple URIs can be passed nested into the NFC_ATTR_LLC_SDP attribute
using the NFC_CMD_LLC_SDREQ netlink command.
When the SNL reply is received, a NFC_EVENT_LLC_SDRES event is sent to
the user space. URI and SAP tuples are passed back, nested into
NFC_ATTR_LLC_SDP attribute.

Signed-off-by: Thierry Escande &lt;thierry.escande@linux.intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Service Name Lookup SDRES aggregation</title>
<updated>2013-03-10T22:10:55+00:00</updated>
<author>
<name>Thierry Escande</name>
<email>thierry.escande@linux.intel.com</email>
</author>
<published>2013-02-15T09:43:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e0ae7bac06ccb90bb0cf7a3362730b48c7d7f1a8'/>
<id>urn:sha1:e0ae7bac06ccb90bb0cf7a3362730b48c7d7f1a8</id>
<content type='text'>
This modifies the way SDRES PDUs are sent back. If multiple SDREQs are
received within a single SNL PDU, all SDRES replies are sent packed in
one SNL PDU too.

Signed-off-by: Thierry Escande &lt;thierry.escande@linux.intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Use socket specific link parameters before the local ones</title>
<updated>2013-03-10T21:20:05+00:00</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2013-02-22T10:38:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=06d44f806aafdafefec789583aba5f8bef301c0c'/>
<id>urn:sha1:06d44f806aafdafefec789583aba5f8bef301c0c</id>
<content type='text'>
If the socket link options are set, use them before the local one.

Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: llcp: Rename socket rw and miu fields</title>
<updated>2013-03-10T21:20:05+00:00</updated>
<author>
<name>Samuel Ortiz</name>
<email>sameo@linux.intel.com</email>
</author>
<published>2013-02-22T00:12:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e4306bec47fc02178c612879c848d3a6544424dd'/>
<id>urn:sha1:e4306bec47fc02178c612879c848d3a6544424dd</id>
<content type='text'>
They really are remote peer parameters, and we need to distinguish them
from the local ones as we'll modify the latter with socket options.

Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>NFC: Add support for SO_TIMESTAMP LLCP socket option</title>
<updated>2013-01-09T23:44:24+00:00</updated>
<author>
<name>Thierry Escande</name>
<email>thierry.escande@linux.intel.com</email>
</author>
<published>2012-11-27T14:44:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.rulkc.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2c2d45bdcb7063ef58dc2c27d72026c394a8f584'/>
<id>urn:sha1:2c2d45bdcb7063ef58dc2c27d72026c394a8f584</id>
<content type='text'>
Set timestamp in sent and received sk_buffs. timestamp is then put in
msghdr structure in llcp_sock_recvmsg().

Signed-off-by: Thierry Escande &lt;thierry.escande@linux.intel.com&gt;
Signed-off-by: Samuel Ortiz &lt;sameo@linux.intel.com&gt;
</content>
</entry>
</feed>
