linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: marcel@holtmann.org
Cc: jukka.rissanen@linux.intel.com,
	linux-zigbee-devel@lists.sourceforge.net,
	linux-bluetooth@vger.kernel.org,
	Alexander Aring <alex.aring@gmail.com>
Subject: [PATCH bluetooth-next 7/7] 6lowpan: remove unused LOWPAN_FRAG_SIZE define
Date: Tue, 29 Jul 2014 23:47:04 +0200	[thread overview]
Message-ID: <1406670424-15596-8-git-send-email-alex.aring@gmail.com> (raw)
In-Reply-To: <1406670424-15596-1-git-send-email-alex.aring@gmail.com>

This define is unused since commit
96cb3eb7a1a5f0c3598500a2348f7d2cc76afbd2 ("6lowpan: fix fragmentation on
sending side"). It is a worst case scenario for payload calculation.
Since commit 96cb3eb7a1a5f0c3598500a2348f7d2cc76afbd2 we calculation the
payload to use the optimal size.

This define is also necessary for ieee802154 6lowpan only and the file
include/net/6lowpan.h should contain generic 6lowpan things only.

Signed-off-by: Alexander Aring <alex.aring@gmail.com>
---
 include/net/6lowpan.h | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/include/net/6lowpan.h b/include/net/6lowpan.h
index 18010bc..3bb3503 100644
--- a/include/net/6lowpan.h
+++ b/include/net/6lowpan.h
@@ -155,17 +155,6 @@
 #define LOWPAN_FRAGN_HEAD_SIZE	0x5
 
 /*
- * According IEEE802.15.4 standard:
- *   - MTU is 127 octets
- *   - maximum MHR size is 37 octets
- *   - MFR size is 2 octets
- *
- * so minimal payload size that we may guarantee is:
- *   MTU - MHR - MFR = 88 octets
- */
-#define LOWPAN_FRAG_SIZE	88
-
-/*
  * Values of fields within the IPHC encoding first byte
  * (C stands for compressed and I for inline)
  */
-- 
2.0.3

  parent reply	other threads:[~2014-07-29 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 21:46 [PATCH bluetooth-next 0/7] 6lowpan: trivial iphc changes Alexander Aring
2014-07-29 21:46 ` [PATCH bluetooth-next 1/7] 6lowpan: iphc: rename hc06_ptr pointer to hc_ptr Alexander Aring
2014-07-29 21:46 ` [PATCH bluetooth-next 2/7] 6lowpan: iphc: use sizeof in udp uncompression Alexander Aring
2014-07-29 21:47 ` [PATCH bluetooth-next 3/7] 6lowpan: iphc: cleanup use of lowpan_fetch_skb Alexander Aring
2014-07-29 21:47 ` [PATCH bluetooth-next 4/7] 6lowpan: iphc: cleanup use of lowpan_push_hc_data Alexander Aring
2014-07-29 21:47 ` [PATCH bluetooth-next 5/7] 6lowpan: iphc: use ipv6 api to check address scope Alexander Aring
2014-07-29 21:47 ` [PATCH bluetooth-next 6/7] 6lowpan: iphc: remove check on null Alexander Aring
2014-07-29 21:47 ` Alexander Aring [this message]
2014-07-30  1:47 ` [PATCH bluetooth-next 0/7] 6lowpan: trivial iphc changes Marcel Holtmann

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=1406670424-15596-8-git-send-email-alex.aring@gmail.com \
    --to=alex.aring@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-zigbee-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.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).