From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH v2 2/7] module: add extra argument for parse_params() callback
Date: Mon, 06 Oct 2014 23:06:34 +0200 [thread overview]
Message-ID: <5433045A.9000108@users.sourceforge.net> (raw)
In-Reply-To: <20141006203823.GB14081@wotan.suse.de>
>> How do you think about to work with more data type definitions for such
>> callback functions?
>
> Sorry I don't understand what you mean.
Can a specific "typedef" help in corresponding software maintenance?
Do you find descriptions from an other software application useful for such an
use case here?
http://www.fltk.org/doc-1.3/group__callback__functions.html
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Tom Gundersen <teg@jklm.no>,
Rusty Russell <rusty@rustcorp.com.au>,
Felipe Contreras <felipe.contreras@gmail.com>,
Davidlohr Bueso <dbueso@suse.de>, Takashi Iwai <tiwai@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Werner Fink <werner@suse.de>,
linux-kernel@vger.kernel.org, Ewan Milne <emilne@redhat.com>,
Oleg Nesterov <oleg@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Santosh Rastapur <santosh@chelsio.com>,
Petr Mladek <pmladek@suse.cz>, Robert Milasan <rmilasan@suse.com>,
Hannes Reinecke <hare@suse.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Coccinelle <cocci@systeme.lip6.fr>,
Jean Delvare <jdelvare@suse.de>,
Benjamin Poirier <bpoirier@suse.de>
Subject: Re: [Cocci] [PATCH v2 2/7] module: add extra argument for parse_params() callback
Date: Mon, 06 Oct 2014 23:06:34 +0200 [thread overview]
Message-ID: <5433045A.9000108@users.sourceforge.net> (raw)
In-Reply-To: <20141006203823.GB14081@wotan.suse.de>
>> How do you think about to work with more data type definitions for such
>> callback functions?
>
> Sorry I don't understand what you mean.
Can a specific "typedef" help in corresponding software maintenance?
Do you find descriptions from an other software application useful for such an
use case here?
http://www.fltk.org/doc-1.3/group__callback__functions.html
Regards,
Markus
next prev parent reply other threads:[~2014-10-06 21:06 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 21:44 [PATCH v2 0/7] driver-core: async probe support Luis R. Rodriguez
2014-10-03 21:44 ` [PATCH v2 1/7] taint: add TAINT_DEBUG for invasive debugging features Luis R. Rodriguez
2014-10-15 5:35 ` Rusty Russell
2014-10-20 20:37 ` Luis R. Rodriguez
2014-10-03 21:44 ` [Cocci] [PATCH v2 2/7] module: add extra argument for parse_params() callback Luis R. Rodriguez
2014-10-03 21:44 ` Luis R. Rodriguez
2014-10-04 12:55 ` [Cocci] " SF Markus Elfring
2014-10-04 12:55 ` SF Markus Elfring
2014-10-06 20:38 ` Luis R. Rodriguez
2014-10-06 20:38 ` Luis R. Rodriguez
2014-10-06 21:06 ` SF Markus Elfring [this message]
2014-10-06 21:06 ` SF Markus Elfring
2014-10-06 22:15 ` Luis R. Rodriguez
2014-10-06 22:15 ` Luis R. Rodriguez
2014-10-15 5:35 ` Rusty Russell
2014-10-15 5:35 ` Rusty Russell
2014-10-03 21:44 ` [PATCH v2 3/7] driver-core: enable drivers to opt-out of async probe Luis R. Rodriguez
2014-10-03 21:44 ` [PATCH v2 4/7] amd64_edac: enforce synchronous probe Luis R. Rodriguez
2014-10-03 21:44 ` [PATCH v2 5/7] driver-core: generalize freeing driver private member Luis R. Rodriguez
2014-10-03 21:44 ` [PATCH v2 6/7] driver-core: add driver module asynchronous probe support Luis R. Rodriguez
2014-10-03 21:44 ` Luis R. Rodriguez
2014-10-03 21:44 ` [PATCH v2 7/7] driver-core: add preferred async probe option for built-in and modules Luis R. Rodriguez
2014-10-03 21:44 ` Luis R. Rodriguez
2014-10-06 20:19 ` Tejun Heo
2014-10-06 20:19 ` Tejun Heo
2014-10-06 20:19 ` Tejun Heo
2014-10-06 20:36 ` Luis R. Rodriguez
2014-10-06 20:36 ` Luis R. Rodriguez
2014-10-06 20:36 ` Luis R. Rodriguez
2014-10-06 21:01 ` Tejun Heo
2014-10-06 21:01 ` Tejun Heo
2014-10-06 21:01 ` Tejun Heo
2014-10-06 23:10 ` Luis R. Rodriguez
2014-10-06 23:10 ` Luis R. Rodriguez
2014-10-06 23:10 ` Luis R. Rodriguez
2014-10-07 17:34 ` Tejun Heo
2014-10-07 17:34 ` Tejun Heo
2014-10-07 17:34 ` Tejun Heo
2014-10-07 17:50 ` Luis R. Rodriguez
2014-10-07 17:50 ` Luis R. Rodriguez
2014-10-07 17:50 ` Luis R. Rodriguez
2014-10-07 17:55 ` Tejun Heo
2014-10-07 17:55 ` Tejun Heo
2014-10-07 17:55 ` Tejun Heo
2014-10-07 18:55 ` Luis R. Rodriguez
2014-10-07 18:55 ` Luis R. Rodriguez
2014-10-07 18:55 ` Luis R. Rodriguez
2014-10-07 19:07 ` Luis R. Rodriguez
2014-10-07 19:07 ` Luis R. Rodriguez
2014-10-07 19:07 ` Luis R. Rodriguez
2014-10-06 20:41 ` Dmitry Torokhov
2014-10-06 20:41 ` Dmitry Torokhov
2014-10-06 20:41 ` Dmitry Torokhov
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=5433045A.9000108@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/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.