From: Paul Moore <pmoore@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] cipso: simplify cipso_v4_translate() when !CONFIG_NETLABEL
Date: Wed, 20 Nov 2013 15:09:55 -0500 [thread overview]
Message-ID: <1786707.gpV9S7REAB@sifl> (raw)
In-Reply-To: <20131120.150620.1185820553046155927.davem@davemloft.net>
On Wednesday, November 20, 2013 03:06:20 PM David Miller wrote:
> From: Paul Moore <pmoore@redhat.com>
> Date: Wed, 20 Nov 2013 14:59:33 -0500
>
> > On Wednesday, November 20, 2013 02:55:11 PM David Miller wrote:
> >> 1) This is a cleanup, and therefore not suitable for submission right now
> >> because the net-next tree is closed.
> >
> > I wasn't expecting it to go into the current merge window, I was just
> > sending it out now so you'd have it for when things started moving again.
> > Think of it as spreading the pain out a bit.
>
> When the merge window opens, I make an announcement here on the list
> politely asking pople to defer net-next patch submissions until after
> the merge window closes and I explicitly announce that net-next is
> open again.
My apologies, I missed that. Subscribed to too many mailing lists and too
reliant on my filters to catch the important bits.
> >> 2) A more suitable commit log message would have been "Don't needlessly
> >> recompute 'opt[opt_iter + 1]' as we already have it stored in
> >> tag_len".
> >>
> >> Then anyone who reads this commit message can say "yes, obviously this
> >> is a correct change and matches what the patch is doing"
> >
> > Fair enough. Do you want a resubmit with your wording once the merge
> > window closes?
>
> ... and I announce that net-next is open once more, yes. Thank you.
Will do.
--
paul moore
security and virtualization @ redhat
prev parent reply other threads:[~2013-11-20 20:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 19:25 [PATCH] cipso: simplify cipso_v4_translate() when !CONFIG_NETLABEL Paul Moore
2013-11-20 19:34 ` David Miller
2013-11-20 19:45 ` Paul Moore
2013-11-20 19:55 ` David Miller
2013-11-20 19:59 ` Paul Moore
2013-11-20 20:06 ` David Miller
2013-11-20 20:09 ` Paul Moore [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=1786707.gpV9S7REAB@sifl \
--to=pmoore@redhat.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