All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] threadsafe rules iteration
Date: Fri, 05 Sep 2008 15:08:55 +0000	[thread overview]
Message-ID: <48C14B87.5060406@tuffmail.co.uk> (raw)
In-Reply-To: <48C113FC.3080203@tuffmail.co.uk>

Alan Jenkins wrote:
> Move ->current out of struct udev_rules and into a new struct udev_rules_iter.
>
> Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
>
> diff --git a/udev/udev_rules.c b/udev/udev_rules.c
> index da7a62a..c21d762 100644
> --- a/udev/udev_rules.c
> +++ b/udev/udev_rules.c
>   

> @@ -1561,14 +1562,15 @@ int udev_rules_get_name(struct udev_rules *rules, struct udevice *udev)
>  
>  int udev_rules_get_run(struct udev_rules *rules, struct udevice *udev)
>  {
> +	struct udev_rules_iter *iter;
>   

Sorry, don't apply that.  It should be

	struct udev_rules_iter iter;


I think we should be building with -Werror, but I'm not sure how to tell
autoconf/automake.

udev_rules.c: In function ‘udev_rules_get_run’:
udev_rules.c:1571: warning: passing argument 1 of ‘udev_rules_iter_init’
from incompatible pointer type
udev_rules.c:1573: warning: passing argument 1 of ‘udev_rules_iter_next’
from incompatible pointer type
udev_rules.c:1624: warning: passing argument 1 of
‘udev_rules_iter_label’ from incompatible pointer type



  reply	other threads:[~2008-09-05 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 11:11 [PATCH] threadsafe rules iteration Alan Jenkins
2008-09-05 15:08 ` Alan Jenkins [this message]
2008-09-08  9:55 ` Scott James Remnant
2008-09-08 10:45 ` Alan Jenkins
2008-09-08 19:38 ` Kay Sievers
2008-09-08 20:07 ` Alan Jenkins
2008-09-08 22:11 ` Kay Sievers

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=48C14B87.5060406@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.