netdev - Re: [PATCH] bpf: fix trivial comment typo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <563A9D2D.90802@gmail.com>
Date:	Thu, 5 Nov 2015 11:05:01 +1100
From:	Matthew Fernandez <matthew.fernandez@...il.com>
To:	Daniel Borkmann <daniel@...earbox.net>,
	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, trivial@...nel.org, ast@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] bpf: fix trivial comment typo

On 03/11/15 20:48, Daniel Borkmann wrote:
> On 11/02/2015 10:48 PM, Matthew Fernandez wrote:
>> On 03/11/15 08:31, David Miller wrote:
>>> From: Matthew Fernandez <matthew.fernandez@...il.com>
>>> Date: Mon, 2 Nov 2015 11:59:03 +1100
>>>
>>>> bpf: fix trivial comment typo
>>>>
>>>> Signed-off-by: Matthew Fernandez <matthew.fernandez@...il.com>
>>>
>>> This doesn't apply to any tree.
>>
>> I'm sorry, I think I must be missing something. This seems to apply cleanly to the current tip of
>> mainline (e86328c489d7) to me. Was this not in the expected format? It wasn't my intention to
>> waste your time, so I apologise for any newbie errors.
>
> You might want to check Documentation/networking/netdev-FAQ.txt ;),
> and rebase your spelling fix f.e. to the latest net-next tree.

Ah right, sorry about that. Thanks for the info, Daniel. From netdev-FAQ it sounds like this patch 
would be more appropriate for the net tree, but as the target file is identical in both right now 
I'll leave it to someone else's discretion to decide which is more suitable. Will rebase and resubmit.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html