netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Derek.Chickles@caviumnetworks.com
Cc: Raghu.Vatsavayi@caviumnetworks.com, netdev@vger.kernel.org,
	Satananda.Burla@caviumnetworks.com,
	Felix.Manlunas@caviumnetworks.com
Subject: Re: [PATCH net-next v7] Add support of Cavium Liquidio ethernet adapters
Date: Mon, 27 Apr 2015 13:22:42 -0400 (EDT)	[thread overview]
Message-ID: <20150427.132242.1898729531212160949.davem@davemloft.net> (raw)
In-Reply-To: <BY1PR0701MB1706783543EEC1BED49CEE84FEE90@BY1PR0701MB1706.namprd07.prod.outlook.com>

From: "Chickles, Derek" <Derek.Chickles@caviumnetworks.com>
Date: Mon, 27 Apr 2015 17:04:35 +0000

> 
>> >>
>> >> It is extremely disappointing that you've defined your own debug
>> >> logging macros, which use generic dev_*() printks, instead of using
>> >> the proper netdev_*() printk logging interfaces to do this.
>> >
>> > We can make this change. I'm not sure why it was missed since we
>> > have netif_level support. Please note, we will still need to use the
>> > dev_ macros for those places in the driver where we don't have a
>> > netdev yet.
>> 
>> Of course.
>> 
>> But there is no reason to go through a special locally defined
>> macros to do this stuff.  Just invoke dev_* and netdev_* directly.
> 
> I think the main reason we're doing this is because we're passing around
> struct octeon_device (which has a pcI_dev pointer and a netdev pointer)
> through some parts of the code and felt the consistency in the printk
> interface was better than having extra pointer dereferences (like
> &oct->pci_dev->dev) inline in the code.  Do you mind if we keep wrappers
> for those pieces? The other places where netdev is immediately available
> can easily be changed.

I don't think this is reasonable.

You can always get to the octeon_device object from the netdev pointer,
so pass that everywhere.

  reply	other threads:[~2015-04-27 17:22 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24  3:19 [PATCH v2] Add support of Cavium Liquidio ethernet adapters Raghu Vatsavayi
2014-11-24 20:52 ` Daniel Borkmann
2014-11-24 21:01 ` Florian Fainelli
2014-11-24 21:08   ` David Miller
2014-12-01 19:57     ` Vatsavayi, Raghu
2014-12-19  3:25       ` [PATCH net-next v3] " Raghu Vatsavayi
2014-12-19  6:59         ` Stephen Hemminger
2014-12-19 17:54           ` Chickles, Derek
2014-12-19  7:01         ` Stephen Hemminger
2014-12-19  7:03         ` Stephen Hemminger
2014-12-19  7:05         ` Stephen Hemminger
2014-12-19  7:07         ` Stephen Hemminger
2014-12-19  7:11         ` Stephen Hemminger
2014-12-19  7:14         ` Stephen Hemminger
2014-12-19  7:21         ` Stephen Hemminger
2014-12-19  7:23         ` Stephen Hemminger
2014-12-19  7:26         ` Stephen Hemminger
2014-12-19  7:28         ` Stephen Hemminger
2014-12-19 18:39           ` Chickles, Derek
2014-12-19 20:53             ` Stephen Hemminger
2014-12-19 20:44         ` Lino Sanfilippo
2014-12-19 20:54           ` Stephen Hemminger
2014-12-19 21:00             ` Lino Sanfilippo
2014-12-19 21:07               ` Lino Sanfilippo
2014-12-19 21:14         ` Lino Sanfilippo
2014-12-19 21:48         ` Lino Sanfilippo
2014-12-19 22:39           ` Chickles, Derek
2014-12-19 22:04         ` Lino Sanfilippo
2014-12-19 22:20           ` Chickles, Derek
2014-12-19 22:24         ` Lino Sanfilippo
2014-12-19 22:53           ` Chickles, Derek
2014-12-19 22:51         ` Lino Sanfilippo
2014-12-20  0:47           ` Chickles, Derek
2015-01-31  2:29             ` [PATCH net-next v4] " Raghu Vatsavayi
2015-02-03  3:00               ` David Miller
2015-02-06 20:28                 ` Chickles, Derek
2015-02-12  1:20                   ` [PATCH net-next v5] " Raghu Vatsavayi
2015-02-19 19:36                     ` David Miller
2015-02-19 20:44                       ` Chickles, Derek
2015-02-19 21:21                         ` David Miller
2015-02-19 21:28                           ` Chickles, Derek
2015-04-08 19:08                             ` [PATCH net-next v6] " Raghu Vatsavayi
2015-04-09  0:46                               ` Joe Perches
2015-04-25  0:34                                 ` [PATCH net-next v7] " Raghu Vatsavayi
2015-04-26 20:04                                   ` David Miller
2015-04-27 16:26                                     ` Chickles, Derek
2015-04-27 16:27                                       ` David Miller
2015-04-27 17:04                                         ` Chickles, Derek
2015-04-27 17:22                                           ` David Miller [this message]
2015-06-10  1:15                                             ` [PATCH net-next v8] " Raghu Vatsavayi
2015-06-11  5:45                                               ` David Miller
2014-12-20  0:33         ` [PATCH net-next v3] " Lino Sanfilippo

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=20150427.132242.1898729531212160949.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Derek.Chickles@caviumnetworks.com \
    --cc=Felix.Manlunas@caviumnetworks.com \
    --cc=Raghu.Vatsavayi@caviumnetworks.com \
    --cc=Satananda.Burla@caviumnetworks.com \
    --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).