From: David Miller <davem@davemloft.net>
To: ncardwell@google.com
Cc: netdev@vger.kernel.org, edumazet@google.com, therbert@google.com
Subject: Re: [PATCH] tcp: restore formatting of macros for tcp_skb_cb sacked field
Date: Mon, 16 Apr 2012 14:49:49 -0400 (EDT) [thread overview]
Message-ID: <20120416.144949.1178765872497298057.davem@davemloft.net> (raw)
In-Reply-To: <1334596086-22905-1-git-send-email-ncardwell@google.com>
From: Neal Cardwell <ncardwell@google.com>
Date: Mon, 16 Apr 2012 13:08:06 -0400
> Commit b82d1bb4 inadvertendly placed unrelated new code between
> TCPCB_EVER_RETRANS and TCPCB_RETRANS and the other macros that refer
> to the sacked field in the struct tcp_skb_cb (probably because there
> was a misleading empty line there). This commit fixes up the
> formatting so that all macros related to the sacked field are adjacent
> again.
>
> Signed-off-by: Neal Cardwell <ncardwell@google.com>
Applied to net-next, thanks Neal.
prev parent reply other threads:[~2012-04-16 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 17:08 [PATCH] tcp: restore formatting of macros for tcp_skb_cb sacked field Neal Cardwell
2012-04-16 18:49 ` David Miller [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=20120416.144949.1178765872497298057.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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).