From: SF Markus Elfring <elfring@users.sourceforge.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-kernel@vger.kernel.org, Coccinelle <cocci@systeme.lip6.fr>,
Arjan van de Ven <arjan@linux.intel.com>,
Benjamin Poirier <bpoirier@suse.de>,
Christoph Hellwig <hch@infradead.org>,
Davidlohr Bueso <dbueso@suse.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Ewan Milne <emilne@redhat.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
Hannes Reinecke <hare@suse.de>, Jean Delvare <jdelvare@suse.de>,
Oleg Nesterov <oleg@redhat.com>, Petr Mladek <pmladek@suse.cz>,
Robert Milasan <rmilasan@suse.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Santosh Rastapur <santosh@chelsio.com>,
Takashi Iwai <tiwai@suse.de>, Tom Gundersen <teg@jklm.no>,
Werner Fink <werner@suse.de>
Subject: Re: [Cocci] [PATCH v2 2/7] module: add extra argument for parse_params() callback
Date: Sat, 04 Oct 2014 14:55:38 +0200 [thread overview]
Message-ID: <542FEE4A.4040401@users.sourceforge.net> (raw)
In-Reply-To: <1412372683-2003-3-git-send-email-mcgrof@do-not-panic.com>
> This adds an extra argument onto parse_params() to be used
> as a way to make the unused callback a bit more useful and
> generic by allowing the caller to pass on a data structure
> of its choice.
How do you think about to work with more data type definitions for such callback
functions?
Regards,
Markus
next prev parent reply other threads:[~2014-10-04 12:56 UTC|newest]
Thread overview: 25+ 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 ` [PATCH v2 2/7] module: add extra argument for parse_params() callback Luis R. Rodriguez
2014-10-04 12:55 ` SF Markus Elfring [this message]
2014-10-06 20:38 ` [Cocci] " Luis R. Rodriguez
2014-10-06 21:06 ` SF Markus Elfring
2014-10-06 22:15 ` Luis R. Rodriguez
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 ` [PATCH v2 7/7] driver-core: add preferred async probe option for built-in and modules Luis R. Rodriguez
2014-10-06 20:19 ` Tejun Heo
2014-10-06 20:36 ` Luis R. Rodriguez
2014-10-06 21:01 ` Tejun Heo
2014-10-06 23:10 ` Luis R. Rodriguez
2014-10-07 17:34 ` Tejun Heo
2014-10-07 17:50 ` Luis R. Rodriguez
2014-10-07 17:55 ` Tejun Heo
2014-10-07 18:55 ` Luis R. Rodriguez
2014-10-07 19:07 ` Luis R. Rodriguez
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=542FEE4A.4040401@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=arjan@linux.intel.com \
--cc=bpoirier@suse.de \
--cc=cocci@systeme.lip6.fr \
--cc=dbueso@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=emilne@redhat.com \
--cc=felipe.contreras@gmail.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=oleg@redhat.com \
--cc=pmladek@suse.cz \
--cc=rmilasan@suse.com \
--cc=rusty@rustcorp.com.au \
--cc=santosh@chelsio.com \
--cc=teg@jklm.no \
--cc=tiwai@suse.de \
--cc=werner@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).