From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Chunyan Zhang <zhang.chunyan@linaro.org>,
laurent.fert@intel.com, yann.fouassier@intel.com,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [QUEUED v20160630 4/4] intel_th: Document output device callbacks
Date: Thu, 30 Jun 2016 15:56:14 +0300 [thread overview]
Message-ID: <1467291374-16587-5-git-send-email-alexander.shishkin@linux.intel.com> (raw)
In-Reply-To: <1467291374-16587-1-git-send-email-alexander.shishkin@linux.intel.com>
'output' type device callbacks are missing from the kerneldoc description
of the 'intel_th_driver' structure. Fix this.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
---
drivers/hwtracing/intel_th/intel_th.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hwtracing/intel_th/intel_th.h b/drivers/hwtracing/intel_th/intel_th.h
index 0482848260..4c195786bf 100644
--- a/drivers/hwtracing/intel_th/intel_th.h
+++ b/drivers/hwtracing/intel_th/intel_th.h
@@ -114,6 +114,9 @@ intel_th_output_assigned(struct intel_th_device *thdev)
* @unassign: deassociate an output type device from an output port
* @enable: enable tracing for a given output device
* @disable: disable tracing for a given output device
+ * @irq: interrupt callback
+ * @activate: enable tracing on the output's side
+ * @deactivate: disable tracing on the output's side
* @fops: file operations for device nodes
* @attr_group: attributes provided by the driver
*
--
2.8.1
prev parent reply other threads:[~2016-06-30 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 12:56 [QUEUED v20160630 0/4] stm class/intel_th: Updates for char-misc-next Alexander Shishkin
2016-06-30 12:56 ` [QUEUED v20160630 1/4] stm class: Add runtime power management handling Alexander Shishkin
2016-06-30 15:19 ` Mathieu Poirier
2016-06-30 15:30 ` Alexander Shishkin
2016-06-30 15:59 ` Mathieu Poirier
2016-07-01 7:10 ` Alexander Shishkin
2016-06-30 12:56 ` [QUEUED v20160630 2/4] intel_th: " Alexander Shishkin
2016-06-30 12:56 ` [QUEUED v20160630 3/4] intel_th: gth: Fix a source comment Alexander Shishkin
2016-07-01 2:37 ` Chunyan Zhang
2016-07-01 7:10 ` Alexander Shishkin
2016-06-30 12:56 ` Alexander Shishkin [this message]
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=1467291374-16587-5-git-send-email-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=greg@kroah.com \
--cc=laurent.fert@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=yann.fouassier@intel.com \
--cc=zhang.chunyan@linaro.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
all inboxes | Powered by JetHome®