All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: linux-arm-kernel@lists.infradead.org, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	rdunlap@infradead.org, Ben.Gainey@arm.com
Subject: [PATCH v2 1/3] coresight: Remove obsolete reference to "owner" in CoreSight descriptor
Date: Tue, 17 Apr 2018 10:08:05 -0600	[thread overview]
Message-ID: <1523981287-15370-2-git-send-email-mathieu.poirier@linaro.org> (raw)
In-Reply-To: <1523981287-15370-1-git-send-email-mathieu.poirier@linaro.org>

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 <mathieu.poirier@linaro.org>
---
 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
 -----------------------------
 
-- 
2.7.4

WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: linux-arm-kernel@lists.infradead.org, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	rdunlap@infradead.org, Ben.Gainey@arm.com
Subject: [PATCH v2 1/3] coresight: Remove obsolete reference to "owner" in CoreSight descriptor
Date: Tue, 17 Apr 2018 10:08:05 -0600	[thread overview]
Message-ID: <1523981287-15370-2-git-send-email-mathieu.poirier@linaro.org> (raw)
In-Reply-To: <1523981287-15370-1-git-send-email-mathieu.poirier@linaro.org>

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 <mathieu.poirier@linaro.org>
---
 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
 -----------------------------
 
-- 
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: mathieu.poirier@linaro.org (Mathieu Poirier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] coresight: Remove obsolete reference to "owner" in CoreSight descriptor
Date: Tue, 17 Apr 2018 10:08:05 -0600	[thread overview]
Message-ID: <1523981287-15370-2-git-send-email-mathieu.poirier@linaro.org> (raw)
In-Reply-To: <1523981287-15370-1-git-send-email-mathieu.poirier@linaro.org>

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 <mathieu.poirier@linaro.org>
---
 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
 -----------------------------
 
-- 
2.7.4

  reply	other threads:[~2018-04-17 16:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 16:08 [PATCH v2 0/3] coresight: Refresh documenation Mathieu Poirier
2018-04-17 16:08 ` Mathieu Poirier
2018-04-17 16:08 ` Mathieu Poirier
2018-04-17 16:08 ` Mathieu Poirier [this message]
2018-04-17 16:08   ` [PATCH v2 1/3] coresight: Remove obsolete reference to "owner" in CoreSight descriptor Mathieu Poirier
2018-04-17 16:08   ` Mathieu Poirier
2018-04-17 16:08 ` [PATCH v2 2/3] coresight: Add section for integration with the perf tools Mathieu Poirier
2018-04-17 16:08   ` Mathieu Poirier
2018-04-17 16:08   ` Mathieu Poirier
2018-04-17 17:26   ` Randy Dunlap
2018-04-17 17:26     ` Randy Dunlap
2018-04-17 17:26     ` Randy Dunlap
2018-04-17 16:08 ` [PATCH v2 3/3] coresight: Grouping all perf tools oriented section together Mathieu Poirier
2018-04-17 16:08   ` Mathieu Poirier
2018-04-17 16:08   ` Mathieu Poirier
2018-04-27 23:00 ` [PATCH v2 0/3] coresight: Refresh documenation Jonathan Corbet
2018-04-27 23:00   ` Jonathan Corbet
2018-04-27 23:00   ` Jonathan Corbet

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=1523981287-15370-2-git-send-email-mathieu.poirier@linaro.org \
    --to=mathieu.poirier@linaro.org \
    --cc=Ben.Gainey@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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.