mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	tony.luck@intel.com, fenghua.yu@intel.com, david@redhat.com,
	tglx@linutronix.de, gregkh@linuxfoundation.org,
	akpm@linux-foundation.org
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] ia64: perfmon: Fix a typo
Date: Mon, 22 Jul 2019 08:56:14 +0200	[thread overview]
Message-ID: <a08f8eff-5043-dcf5-b4e1-22c0512bd8d3@metux.net> (raw)
In-Reply-To: <20190721165144.3152-1-christophe.jaillet@wanadoo.fr>

On 21.07.19 18:51, Christophe JAILLET wrote:
> s/permfon.h/perfmon.h/
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> The reference to perfmon.h should maybe be just removed because I've found
> no information about the increasing order to respect.
> This is maybe now in another file?
> ---
>   arch/ia64/kernel/perfmon.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/ia64/kernel/perfmon.c b/arch/ia64/kernel/perfmon.c
> index 58a6337c0690..22795b420b10 100644
> --- a/arch/ia64/kernel/perfmon.c
> +++ b/arch/ia64/kernel/perfmon.c
> @@ -4550,7 +4550,7 @@ pfm_exit_thread(struct task_struct *task)
>   }
>   
>   /*
> - * functions MUST be listed in the increasing order of their index (see permfon.h)
> + * functions MUST be listed in the increasing order of their index (see perfmon.h)
>    */
>   #define PFM_CMD(name, flags, arg_count, arg_type, getsz) { name, #name, flags, arg_count, sizeof(arg_type), getsz }
>   #define PFM_CMD_S(name, flags) { name, #name, flags, 0, 0, NULL }
> 

Reviewed-By: Enrico Weigelt <info@metux.net>
-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

  reply	other threads:[~2019-07-22  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-21 16:51 Christophe JAILLET
2019-07-22  6:56 ` Enrico Weigelt, metux IT consult [this message]
2019-07-22  6:56 ` Enrico Weigelt, metux IT consult

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=a08f8eff-5043-dcf5-b4e1-22c0512bd8d3@metux.net \
    --to=lkml@metux.net \
    --cc=akpm@linux-foundation.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=david@redhat.com \
    --cc=fenghua.yu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    /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®