From: David Miller <davem@davemloft.net>
To: rami.rosen@intel.com
Cc: sergei.shtylyov@cogentembedded.com, netdev@vger.kernel.org,
johannes.berg@intel.com
Subject: Re: [PATCH net-next] genetlink: remove ops_list from genetlink header.
Date: Sun, 04 Jun 2017 16:25:37 -0400 (EDT) [thread overview]
Message-ID: <20170604.162537.2126286349815789267.davem@davemloft.net> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F93DA1EEFA@HASMSX110.ger.corp.intel.com>
From: "Rosen, Rami" <rami.rosen@intel.com>
Date: Sun, 4 Jun 2017 19:20:43 +0000
> Hi, Sergei,
>
> Thanks! I will send V2 with 12 digits for the commit.
Please never top-post.
prev parent reply other threads:[~2017-06-04 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-04 7:07 [PATCH net-next] genetlink: remove ops_list from genetlink header Rami Rosen
2017-06-04 17:18 ` Sergei Shtylyov
2017-06-04 19:20 ` Rosen, Rami
2017-06-04 20:25 ` David Miller [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=20170604.162537.2126286349815789267.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rami.rosen@intel.com \
--cc=sergei.shtylyov@cogentembedded.com \
/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).