public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Staging: RAR support - bring ready to move from staging
Date: Tue, 4 May 2010 08:51:12 -0700	[thread overview]
Message-ID: <20100504155112.GA26143@kroah.com> (raw)
In-Reply-To: <20100504105032.3de58e68@linux.intel.com>

On Tue, May 04, 2010 at 10:50:32AM +0100, Alan Cox wrote:
> 
> rar: perform a clean up pass
> 
> - Move to a registration model where each RAR is claimed/unclaimed
> - Use that to fix the client stuff (one client per RAR so no need to queue stuff)
> - Support unregister so drivers can rmmod themselves safely
> - Fix locking hang on calling rar lock from rar callback
> - Clean up
> - Kerneldoc

I get the following build errors with this patch:
	  CC [M]  drivers/staging/memrar/memrar_handler.o
	drivers/staging/memrar/memrar_handler.c: In function ‘memrar_init’:
	drivers/staging/memrar/memrar_handler.c:910: warning: passing argument 1 of ‘register_rar’ makes integer from pointer without a cast
	drivers/staging/memrar/../rar_register/rar_register.h:37: note: expected ‘int’ but argument is of type ‘int (*)(void *)’
	drivers/staging/memrar/memrar_handler.c:910: error: too few arguments to function ‘register_rar’
	make[2]: *** [drivers/staging/memrar/memrar_handler.o] Error 1
	make[1]: *** [drivers/staging/memrar] Error 2
	make: *** [_module_drivers/staging] Error 2

Should I have applied your other patch first?

thanks,

greg k-h

  reply	other threads:[~2010-05-04 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04  9:50 PATCH: RAR support - bring ready to move from staging Alan Cox
2010-05-04 15:51 ` Greg KH [this message]
2010-05-04 16:27   ` Staging: " Alan Cox
2010-05-04 17:20     ` Greg KH
2010-05-04 17:30       ` Alan Cox

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=20100504155112.GA26143@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@linux.intel.com \
    --cc=linux-kernel@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