LKML Archive on
help / color / mirror / Atom feed
From: Mathieu Poirier <>
Subject: [PATCH 1/3] coresight: Remove obsolete reference to "owner" in CoreSight descriptor
Date: Mon, 16 Apr 2018 13:35:25 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Field "owner" of struct coresight_desc has been removed a while back but
the documentation was not updated to reflect the changes.

Signed-off-by: Mathieu Poirier <>
 Documentation/trace/coresight.txt | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt
index 6f0120c3a4f1..710c75b6c73f 100644
--- a/Documentation/trace/coresight.txt
+++ b/Documentation/trace/coresight.txt
@@ -187,9 +187,6 @@ that can be performed on them (see "struct coresight_ops").  The
 specific to that component only.  "Implementation defined" customisations are
 expected to be accessed and controlled using those entries.
-Last but not least, "struct module *owner" is expected to be set to reflect
-the information carried in "THIS_MODULE".
 How to use the tracer modules

  reply	other threads:[~2018-04-16 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 19:35 [PATCH 0/3] coresight: Refresh documenation Mathieu Poirier
2018-04-16 19:35 ` Mathieu Poirier [this message]
2018-04-16 19:35 ` [PATCH 2/3] coresight: Add section for integration with the perf tools Mathieu Poirier
2018-04-16 19:48   ` Randy Dunlap
2018-04-17 15:46     ` Mathieu Poirier
2018-04-16 19:35 ` [PATCH 3/3] coresight: Grouping all perf tools oriented section together Mathieu Poirier

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).