From: William Allen Simpson <william.allen.simpson@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next-2.6 PATCH v9 2/2] TCPCT part 1i: remove old tcp_optlen() function
Date: Fri, 04 Dec 2009 07:06:00 -0500 [thread overview]
Message-ID: <4B18FB28.4030707@gmail.com> (raw)
In-Reply-To: <20091203.155651.04450554.davem@davemloft.net>
David Miller wrote:
> These changes are probably fine but are too late for the current
> merge window, please resubmit them (with any requested changes made
> by reviewers) for the next merge window.
>
> Thanks.
>
OK. These were split from the main part 1 sequence (looking back, both
by Ilpo's review at different times), because he objected to "cleanup"
patches being included with "new" features. They've both been in 4 to 6
previous patch variants.
(More review would be good, and I'd be more comfortable with review by
somebody that could actually test this patch. That's why the CC:
according to Documentation/SubmittingPatches part 13.)
I'm a bit unclear on "merge window", and am unable to find information
in the Documentation tree. I see that there was a message that came in
the middle of my patch submission:
Re: README: net-next-2.6 plans...
Trying to understand the process: When I first started sending patches
in early October against the -2.6 tree, I was told privately to make
them against net-next-2.6 instead. Does this mean these "cleanup"
patches should be made for -2.6 now?
prev parent reply other threads:[~2009-12-04 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 23:30 [net-next-2.6 PATCH v9 0/2] TCPCT part 1: cleanup William Allen Simpson
2009-12-03 23:40 ` [net-next-2.6 PATCH v9 0/2] TCPCT part 1h: accept SYNACK data William Allen Simpson
2009-12-03 23:54 ` [net-next-2.6 PATCH v9 2/2] TCPCT part 1i: remove old tcp_optlen() function William Allen Simpson
2009-12-03 23:56 ` David Miller
2009-12-04 12:06 ` William Allen Simpson [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=4B18FB28.4030707@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).