From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: ohci: deprecate debug parameter
Date: Wed, 4 Sep 2024 19:15:03 +0900 [thread overview]
Message-ID: <20240904101503.GB437448@workstation.local> (raw)
In-Reply-To: <20240903101455.317067-1-o-takashi@sakamocchi.jp>
On Tue, Sep 03, 2024 at 07:14:55PM +0900, Takashi Sakamoto wrote:
> Many tracepoints events have been added to 6.10 and 6.11 kernels. They are
> available as an alternative of debug parameter in firewire-ohci module.
>
> The logging messages enabled by the parameter require some cumbersomes in
> a point of maintenance; e.g. the code to decode transaction frame.
>
> This commit adds deprecation text to conduct users to them..
>
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
> drivers/firewire/ohci.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
Applied to for-next branch.
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-09-04 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 10:14 [PATCH] firewire: ohci: deprecate debug parameter Takashi Sakamoto
2024-09-04 10:15 ` Takashi Sakamoto [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=20240904101503.GB437448@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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