Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Dominik Karol Piatkowski <dominik.karol.piatkowski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/1] lib/igt_core.h: Typo fix
Date: Thu, 15 Jun 2023 11:53:11 +0200	[thread overview]
Message-ID: <20230615115311.63dbc485@maurocar-mobl2> (raw)
In-Reply-To: <20230614133301.4888-2-dominik.karol.piatkowski@intel.com>

On Wed, 14 Jun 2023 15:33:01 +0200
Dominik Karol Piatkowski <dominik.karol.piatkowski@intel.com> wrote:

> Fixed IGT_EXIT_ABORT description typo in lib/igt_core.h
> 
> Signed-off-by: Dominik Karol Piątkowski <dominik.karol.piatkowski@intel.com>
> Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>

Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>

> ---
>  lib/igt_core.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/igt_core.h b/lib/igt_core.h
> index ef6bed6a5..26bb0cb68 100644
> --- a/lib/igt_core.h
> +++ b/lib/igt_core.h
> @@ -136,8 +136,8 @@ struct _GKeyFile *igt_load_igtrc(void);
>  /**
>   * IGT_EXIT_ABORT
>   *
> - * Exit status indicating a severe test/enviroment failure, any continued
> - * testing past this point can yeild unexpected reasults and is not recommended
> + * Exit status indicating a severe test/environment failure, any continued
> + * testing past this point can yield unexpected results and is not recommended
>   */
>  #define IGT_EXIT_ABORT 112
>  

  reply	other threads:[~2023-06-15  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 13:33 [igt-dev] [PATCH i-g-t 0/1] lib/igt_core.h: Typo fix Dominik Karol Piatkowski
2023-06-14 13:33 ` [igt-dev] [PATCH i-g-t 1/1] " Dominik Karol Piatkowski
2023-06-15  9:53   ` Mauro Carvalho Chehab [this message]
2023-06-14 15:52 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork

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=20230615115311.63dbc485@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=dominik.karol.piatkowski@intel.com \
    --cc=igt-dev@lists.freedesktop.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