netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, edumazet@google.com, vfalico@redhat.com,
	nicolas.dichtel@6wind.com, stephen@networkplumber.org,
	hkchu@google.com, dborkman@redhat.com, willemb@google.com,
	hannes@stressinduktion.org, atzm@stratosphere.co.jp, phil@nwl.cc,
	richardcochran@gmail.com
Subject: Re: [patch net-next] net: make packet_type->ak_packet_priv generic
Date: Fri, 4 Apr 2014 16:47:17 +0200	[thread overview]
Message-ID: <20140404144717.GC2892@minipsycho.brq.redhat.com> (raw)
In-Reply-To: <20140404.100754.1337061118939924472.davem@davemloft.net>

Fri, Apr 04, 2014 at 04:07:54PM CEST, davem@davemloft.net wrote:
>From: Jiri Pirko <jiri@resnulli.us>
>Date: Fri, 4 Apr 2014 16:03:25 +0200
>
>> Fri, Apr 04, 2014 at 03:54:20PM CEST, davem@davemloft.net wrote:
>>>From: Jiri Pirko <jiri@resnulli.us>
>>>Date: Fri,  4 Apr 2014 14:20:38 +0200
>>>
>>>> The priv is used now by af_packet. Rename it to make it useable for
>>>> others as well. Also, introduce packet_id_match to move the sk matching
>>>> from skb_loop_sk to af_packet code where it belongs.
>>>> 
>>>> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>>>
>>>Firstly, net-next is closed.
>> 
>> Dave, it would be really great if you stick with the same email subject
>> when you declare net-next closed. I was looking for "CLOSED" but now the
>> subject is "no new feature patches please" which I missed.
>
>Sorry, that's not a reasonable request.
>
>It is very clear from the subject line I choose what the message is
>about.  I don't have to use an ALL CAPS subject line "just because"

That was just an example. You used that already, for example:
Date: Tue, 19 Feb 2013 00:56:53 -0500 (EST)
From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: net-next is CLOSED

Please don't get me wrong, I'm just making a suggestion. As Nicolas wrote,
it would save your time. And others as well when they know what to 'grep'.


>
>>>Secondly, submit this with the unmentioned and mysterious "other
>>>user", there currently are none.
>> 
>> There is none atm. But anyway, the struct field name should be generic,
>> cause this is not specific to af_packet. Anybody might want to pass a
>> "priv".
>
>No, because it makes it clear what the one and only user is.

Well there are others which would use this priv as well. For example:
drivers/scsi/bnx2fc/bnx2fc_fcoe.c

They work around this by embedding struct packet_type into their priv and in
_rcv they access it by container_of.

At the end I think it would be nicer to allow struct packet_type to be
defined static by users and pass priv and dev as parameters to dev_add_pack()

>
>Any new user would be seriously frowned upon, because this is
>an easy side channel for proprietary extensions to the networking.

      parent reply	other threads:[~2014-04-04 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 12:20 [patch net-next] net: make packet_type->ak_packet_priv generic Jiri Pirko
2014-04-04 12:58 ` Nicolas Dichtel
2014-04-04 13:23   ` Jiri Pirko
2014-04-04 13:36     ` Nicolas Dichtel
2014-04-04 13:54 ` David Miller
2014-04-04 14:03   ` Jiri Pirko
2014-04-04 14:07     ` David Miller
2014-04-04 14:23       ` Nicolas Dichtel
2014-04-04 14:33         ` Eric Dumazet
2014-04-04 14:47       ` Jiri Pirko [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=20140404144717.GC2892@minipsycho.brq.redhat.com \
    --to=jiri@resnulli.us \
    --cc=atzm@stratosphere.co.jp \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=edumazet@google.com \
    --cc=hannes@stressinduktion.org \
    --cc=hkchu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=phil@nwl.cc \
    --cc=richardcochran@gmail.com \
    --cc=stephen@networkplumber.org \
    --cc=vfalico@redhat.com \
    --cc=willemb@google.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).