From: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/2] net: sched: act_ctinfo: fixes
Date: Tue, 18 Jun 2019 07:33:58 +0000 [thread overview]
Message-ID: <808B8876-3E99-4B3B-9E87-0B5E4BD5F57D@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <20190617.140106.2136391777805798865.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
> On 17 Jun 2019, at 22:01, David Miller <davem@davemloft.net> wrote:
>
> From: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
> Date: Mon, 17 Jun 2019 11:03:25 +0100
>
>>
<snipped>
>> If I ever get to a developer conference please feel free to
>> tar/feather/apply cone of shame.
>
> :-) In kernel networking development we prefer brown paper bags over
> cones of shame, just FYI :) :) :)
LOL - I’ll bear that in mind :-) I thought fixing the code and admitting
my incompetence was the best policy…I’d be found out at some point anyway :-)
>
> Series applied, thanks.
Excellent. Hopefully that will be it.
Cheers,
Kevin D-B
gpg: 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-06-18 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 10:03 [PATCH net-next 0/2] net: sched: act_ctinfo: fixes Kevin Darbyshire-Bryant
2019-06-17 10:03 ` [PATCH net-next 1/2] net: sched: act_ctinfo: fix action creation Kevin Darbyshire-Bryant
2019-06-17 10:03 ` [PATCH net-next 2/2] net: sched: act_ctinfo: fix policy validation Kevin Darbyshire-Bryant
2019-06-17 21:01 ` [PATCH net-next 0/2] net: sched: act_ctinfo: fixes David Miller
2019-06-18 7:33 ` Kevin 'ldir' Darbyshire-Bryant [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=808B8876-3E99-4B3B-9E87-0B5E4BD5F57D@darbyshire-bryant.me.uk \
--to=ldir@darbyshire-bryant.me.uk \
--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).