From: Saeed Mahameed <saeedm@mellanox.com>
To: Jiri Pirko <jiri@resnulli.us>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: net-next STATUS page
Date: Thu, 13 Jul 2017 14:32:48 +0300 [thread overview]
Message-ID: <572310a4-5914-52d2-6688-c899f3c7f245@mellanox.com> (raw)
In-Reply-To: <20170713085639.GA2060@nanopsycho>
On 7/13/2017 11:56 AM, Jiri Pirko wrote:
> Tue, Jul 11, 2017 at 08:58:41PM CEST, stephen@networkplumber.org wrote:
>> On Tue, 11 Jul 2017 07:24:16 -0700 (PDT)
>> David Miller <davem@davemloft.net> wrote:
>>
>>> It has gotten to the point that even casually walking around
>>> Faro, Portugal last week, random German tourists would stop
>>> me in the street and ask if net-next was open or not.
>>>
>>> Therefore, in order to avoid any and all confusion I have created this
>>> web site:
>>>
>>> https://emea01.safelinks.protection.outlook.com/?url=http:%2F%2Fvger.kernel.org%2F~davem%2Fnet-next.html&data=02%7C01%7Csaeedm%40mellanox.com%7Caf800791df264ccd4eb008d4c9cd20ca%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636355330266033104&sdata=frov8YFnlybI1n3hacYLWJZzYbWL7mk4kWIS6XlG2Vg%3D&reserved=0
>>>
>>> Please refer to it if you are ever in doubt.
>>>
>>> Thanks!
>>
>> Where is the app?
>
> There would be good to have git-send-email hook to check this :)
>
You will need an image processing algorithm to determine whether it is
open or close, i have some good neural network algorithms if you are
interested :)
next prev parent reply other threads:[~2017-07-13 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 14:24 net-next STATUS page David Miller
2017-07-11 15:05 ` Jiri Pirko
2017-07-11 15:15 ` Phil Sutter
2017-07-11 16:49 ` Cong Wang
2017-07-11 18:58 ` Stephen Hemminger
2017-07-13 8:56 ` Jiri Pirko
2017-07-13 11:32 ` Saeed Mahameed [this message]
2017-07-13 11:47 ` Jan Engelhardt
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=572310a4-5914-52d2-6688-c899f3c7f245@mellanox.com \
--to=saeedm@mellanox.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=stephen@networkplumber.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).