linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Flavio Suligoi <f.suligoi@asem.it>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] tty: fix spelling mistake
Date: Tue, 09 Jun 2020 10:37:01 -0700	[thread overview]
Message-ID: <64758b6f2142a1b2a170de38b80f2dbe6c70ceb2.camel@perches.com> (raw)
In-Reply-To: <20200609160249.31329-1-f.suligoi@asem.it>

On Tue, 2020-06-09 at 18:02 +0200, Flavio Suligoi wrote:
> Fix typo: "tigger" --> "trigger"

Thanks.

fyi:

$ git grep -w -i tigger
drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core.c:                       * software tigger (systrig, hrtimer).
drivers/leds/led-triggers.c:/* Simple LED Tigger Interface */
drivers/scsi/mpt3sas/mpt3sas_trigger_diag.h:/* fake firmware event for tigger */
drivers/tty/moxa.h:#define IntrRxTrigger        0x100   /* rx data count reach tigger value */
kernel/trace/trace.c:    * to store the trace event for the tigger to use. It's recusive
tools/testing/selftests/ftrace/test.d/trigger/trigger-hist.tc:echo "Test histogram basic tigger"
tools/testing/selftests/ftrace/test.d/trigger/trigger-stacktrace.tc:echo "Test stacktrace tigger"
tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-hist.tc:echo "Test histogram trace_marker tigger"
tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-snapshot.tc:echo "Test snapshot trace_marker tigger"




  reply	other threads:[~2020-06-09 17:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 16:02 [PATCH 1/1] tty: fix spelling mistake Flavio Suligoi
2020-06-09 17:37 ` Joe Perches [this message]
2020-06-09 19:35   ` Jiri Slaby
2020-06-10 10:02     ` Flavio Suligoi
2020-06-10  7:12   ` Flavio Suligoi

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=64758b6f2142a1b2a170de38b80f2dbe6c70ceb2.camel@perches.com \
    --to=joe@perches.com \
    --cc=f.suligoi@asem.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.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 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).