linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 12/16] iwlwifi: dbg_ini: support domain changing via debugfs
Date: Wed, 16 Oct 2019 10:07:15 +0300	[thread overview]
Message-ID: <87pnixkw2k.fsf@codeaurora.org> (raw)
In-Reply-To: <20191014101813.7e2742c1e22f.I65d0d5e782864f53b4ed8a6f43e72c50a09d9fd9@changeid> (Luca Coelho's message of "Mon, 14 Oct 2019 10:20:15 +0300")

Luca Coelho <luca@coelho.fi> writes:

> From: Shahar S Matityahu <shahar.s.matityahu@intel.com>
>
> Allow to change or read the debug domain bitmap at runtime via
> fw_dbg_domain debugfs.
>
> Signed-off-by: Shahar S Matityahu <shahar.s.matityahu@intel.com>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>

[...]

> +static ssize_t iwl_dbgfs_fw_dbg_domain_write(struct iwl_fw_runtime *fwrt,
> +					     char *buf, size_t count)
> +{
> +	u32 new_domain;
> +	long val;
> +	int ret;
> +
> +	if (!iwl_trans_fw_running(fwrt->trans))
> +		return -EIO;
> +
> +	ret = kstrtol(buf, 0, &val);
> +	if (ret)
> +		return ret;
> +
> +	new_domain = (u32)val;

Why not use kstrtou32()? Then there's no need to cast anything.

-- 
Kalle Valo

  reply	other threads:[~2019-10-16  7:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14  7:20 [PATCH v2 00/16] iwlwifi: updates intended for v5.5 2019-10-12-v2 Luca Coelho
2019-10-14  7:20 ` [PATCH v2 01/16] iwlwifi: dbg_ini: load external dbg cfg after internal cfg is loaded Luca Coelho
2019-10-14  7:20 ` [PATCH v2 02/16] iwlwifi: dbg_ini: use new region TLV in dump flow Luca Coelho
2019-10-14  7:20 ` [PATCH v2 03/16] iwlwifi: dbg_ini: use new trigger " Luca Coelho
2019-10-18  8:25   ` Luca Coelho
2019-10-14  7:20 ` [PATCH v2 04/16] iwlwifi: dbg: remove multi buffers infra Luca Coelho
2019-10-14  7:20 ` [PATCH v2 05/16] iwlwifi: dbg_ini: add monitor dumping support Luca Coelho
2019-10-14  7:20 ` [PATCH v2 06/16] iwlwifi: dbg_ini: add error tables " Luca Coelho
2019-10-14  7:20 ` [PATCH v2 07/16] iwlwifi: dbg_ini: use new API in dump info Luca Coelho
2019-10-14  7:20 ` [PATCH v2 08/16] iwlwifi: dbg_ini: add TLV allocation new API support Luca Coelho
2019-10-14  7:20 ` [PATCH v2 09/16] iwlwifi: dbg_ini: implement time point handling Luca Coelho
2019-10-14  7:20 ` [PATCH v2 10/16] iwlwifi: dbg_ini: implement monitor allocation flow Luca Coelho
2019-10-14  7:20 ` [PATCH v2 11/16] iwlwifi: dbg_ini: add periodic trigger new API support Luca Coelho
2019-10-14  7:20 ` [PATCH v2 12/16] iwlwifi: dbg_ini: support domain changing via debugfs Luca Coelho
2019-10-16  7:07   ` Kalle Valo [this message]
2019-10-18  8:30     ` Luca Coelho
2019-10-18  8:40   ` [PATCH v2 03/16] " Luca Coelho
2019-10-14  7:20 ` [PATCH v2 13/16] iwlwifi: dbg_ini: support FW response/notification region type Luca Coelho
2019-10-14  7:20 ` [PATCH v2 14/16] iwlwifi: dbg_ini: rename external debug configuration file Luca Coelho
2019-10-14  7:20 ` [PATCH v2 15/16] iwlwifi: dbg_ini: remove old API and some related code Luca Coelho
2019-10-14  7:20 ` [PATCH v2 16/16] iwlwifi: dbg_ini: support FW notification dumping in case of missed beacon Luca Coelho

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=87pnixkw2k.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    /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).