From: Junho Lee <tot0roprog@gmail.com>
To: Brian Gix <bggixx@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/4] mesh: Implement lower transport layer for segmentation and reassembly
Date: Mon, 14 Oct 2024 14:31:18 +0900 [thread overview]
Message-ID: <670caca9.620a0220.33cf6c.4855@mx.google.com> (raw)
In-Reply-To: <b34b48bb-bf86-4a50-90fb-b0ff147c1be8@gmail.com>
Hi Brian,
On Sun, Oct 13, 2024 at 12:27:18PM -0700, Brian Gix wrote:
> Hi Junho,
>
> There are some check-patch failures on your patchset.
>
> Can you fix these (and any others you find with check-patch) and resubmit?
> The ones below are only from patch 1 of 4... patch 3 applied cleanly, but 2
> and 4 also could not be applied until patch 1 is fixed.
>
> Thanks,
> Brian
>
Sure. I had already fixed that part, but I didn't resubmit it because I
was writing in some unit tests as Luiz advised.
I resubmitted it a while ago, so please check it. If I run into any patch
issues again, I'll fix it and resubmit.
> On 10/4/24 12:31 AM, Junho Lee wrote:
> > - send_net_ack(net, sar_in, expected);
> > + if (sar->flags == expected) {
> > + /*
> > + * According to MshPRTv1.1: 3.5.3.4, if the destination
> > + * is a unicast address and a segment is received for a
> > + * completed message, it sends one acknowledgment within
> > + * a period of:
> > + * [acknowledgment delay increment * segment reception interval]
> WARNING:LONG_LINE_COMMENT: line over 80 characters
> #774: FILE: mesh/net.c:2207:
> + * [acknowledgment delay increment * segment reception
> interval]
>
>
> > /* Msg length only definitive on last segment */
> > if (segO == segN)
> > - sar_in->len = segN * MAX_SEG_LEN + size;
> > + sar->len = segN * MAX_SEG_LEN + size;
> > +
> > + /* Send ACK only if DST is unicast address. */
> > + if(IS_UNICAST(dst)) {
> ERROR:SPACING: space required before the open parenthesis '('
> #875: FILE: mesh/net.c:2283:
> + if(IS_UNICAST(dst)) {
>
> > + * segmented. Flush if it is not segmented or if the transmission
> > + * failed.
> > + */
> > + if (result && segmented) {
> > + struct mesh_sar_tx *sar_tx = mesh_sar_tx_new();
> > + bool is_unicast = IS_UNICAST(dst);
> > + sar_tx->ack_received = false;
> WARNING:LINE_SPACING: Missing a blank line after declarations
> #1010: FILE: mesh/net.c:3565:
> + bool is_unicast = IS_UNICAST(dst);
> + sar_tx->ack_received = false;
>
>
prev parent reply other threads:[~2024-10-14 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 7:31 [PATCH BlueZ 1/4] mesh: Implement lower transport layer for segmentation and reassembly Junho Lee
2024-10-04 8:57 ` mesh: Fix segmentation behavior of Lower transport layer bluez.test.bot
2024-10-13 19:27 ` [PATCH BlueZ 1/4] mesh: Implement lower transport layer for segmentation and reassembly Brian Gix
2024-10-14 5:31 ` Junho Lee [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=670caca9.620a0220.33cf6c.4855@mx.google.com \
--to=tot0roprog@gmail.com \
--cc=bggixx@gmail.com \
--cc=linux-bluetooth@vger.kernel.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