linux-kernel - Re: Re-send (What else needs to be done to the sep driver (staging/sep))

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110413224621.GA4909@kroah.com>
Date:	Wed, 13 Apr 2011 15:46:21 -0700
From:	Greg KH <greg@...ah.com>
To:	Joe Perches <joe@...ches.com>
Cc:	"Mark A. Allyn" <mark.a.allyn@...el.com>,
	linux-kernel@...r.kernel.org, alan@...ux.intel.com,
	jayant.mangalampalli@...el.com, venkat.r.gokulrangan@...el.com
Subject: Re: Re-send (What else needs to be done to the sep driver
 (staging/sep))

On Wed, Apr 13, 2011 at 03:30:36PM -0700, Joe Perches wrote:
> On Wed, 2011-04-13 at 15:23 -0700, Greg KH wrote:
> > Ick, no, never use your own macros, just use the "real" things like is
> > done in this driver.  If it's a pain to get to that pointer, then use a
> > temporary variable in the code and then use it.
> > 
> > Otherwise, no, I don't like this patch at all, sorry.
> 
> I think you're simply incorrect here.
> 
> There are lots of other uses like netdev_<foo>
> where <foo>_<level> takes a particular pointer type.
> 
> This is a structure that contains a pointer to
> another structure than contains a struct device.
> 
> You might also look at the macros the USB subsystem
> uses for message logging.
> 
> Hey, aren't you the USB maintainer?

Yes, and over time we have been moving away from using those macros.  I
don't like seeing every individual driver have its own way of handling
debug macros, that's crazy.

For larger stuff like networking, yes, they can do that, and that's
fine.  They also were doing this before the dev_* macros came along,
just like USB did, so there is historical precident there.

But again, not for a new driver, don't redefine the existing macros just
because you don't like typing a few extra characters...

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/