Re: [patch 3/3] kmsg: convert xpram messages to kmsg api.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Greg KH
Date: Wednesday, July 30, 2008 - 12:43 pm

On Wed, Jul 30, 2008 at 06:56:59PM +0200, Martin Schwidefsky wrote:

Ick, so you are going to have to define a message number per file?
How is that going to work, it looks like you use ids 0-2 below in the .c
file, yet in this documentation file they are 1-3.  Off by one
somewhere?  :)


Any way to put this stuff in the .c file itself?  It's hard enough
getting people to update Documentation/ABI/, knowing to go modify
something else in the Documentation directory is going to be _very_
difficult.



Can't you just use KBUILD_MODULE_NAME instead?  That makes it one less
thing you have to define in the code (and forget about when moving files
around or cut-and-pasting).


Magic number "1" here?  See comment above about this.

thanks,

greg k-h
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch 3/3] kmsg: convert xpram messages to kmsg api., Martin Schwidefsky, (Wed Jul 30, 9:56 am)
Re: [patch 3/3] kmsg: convert xpram messages to kmsg api., Greg KH, (Wed Jul 30, 12:43 pm)
Re: [patch 3/3] kmsg: convert xpram messages to kmsg api., Martin Schwidefsky, (Thu Jul 31, 1:33 am)
Re: [patch 3/3] kmsg: convert xpram messages to kmsg api., Martin Schwidefsky, (Mon Aug 4, 1:06 am)
Re: [patch 3/3] kmsg: convert xpram messages to kmsg api., Martin Schwidefsky, (Wed Aug 6, 1:46 am)
Re: [patch 3/3] kmsg: convert xpram messages to kmsg api., Martin Schwidefsky, (Thu Aug 7, 1:39 am)