Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org,
	Mohammed Anas <triallax@tutanota.com>,
	Stefano Ragni <st3r4g@protonmail.com>,
	Bernd Kuhls <bernd@kuhls.net>,
	Reagan Bohan <xbjfk.github@gmail.com>, Yureka <yuka@yuka.dev>,
	Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Subject: Re: [PATCH i-g-t v1 1/1] tests/intel/kms_pm_backlight: Fixed build on musl
Date: Thu, 22 Aug 2024 20:44:54 +0200	[thread overview]
Message-ID: <3305001.aeNJFYEL58@jkrzyszt-mobl2.ger.corp.intel.com> (raw)
In-Reply-To: <20240821095137.60254-2-kamil.konieczny@linux.intel.com>

Hi Kamil,

On Wednesday, 21 August 2024 11:51:37 GMT+2 Kamil Konieczny wrote:
> Fix compilation on musl by including proper POSIX header for
> basename. Also while at this, sort out other headers.
> 
> Cc: Mohammed Anas <triallax@tutanota.com>
> Cc: Stefano Ragni <st3r4g@protonmail.com>
> Cc: Bernd Kuhls <bernd@kuhls.net>
> Cc: Reagan Bohan <xbjfk.github@gmail.com>
> Reported-by: Yureka <yuka@yuka.dev>
> Signed-off-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> ---
>  tests/intel/kms_pm_backlight.c | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/tests/intel/kms_pm_backlight.c b/tests/intel/kms_pm_backlight.c
> index 8672afa7a..c2213d3b1 100644
> --- a/tests/intel/kms_pm_backlight.c
> +++ b/tests/intel/kms_pm_backlight.c
> @@ -35,15 +35,17 @@
>   * Test category: functionality test
>   */
>  
> -#include "igt.h"
> +#include <unistd.h>

Assuming you tried to follow the linux kernel rule of sorting headers 
alphabetically, why did you place unistd.h at the top?

> +#include <errno.h>
> +#include <fcntl.h>
> +#include <libgen.h> /* for POSIX basename */

LGTM.

>  #include <limits.h>
> +#include <stdio.h>
>  #include <sys/types.h>
>  #include <sys/stat.h>

With still the same assumption, did you notice the above two headers are in 
reverse alphabetic order?

With either the headers in correct alphabetic order, or otherwise the existing 
headers untouched:

Reviewed-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>

Thanks,
Janusz

> -#include <fcntl.h>
> -#include <stdio.h>
> -#include <errno.h>
> -#include <unistd.h>
>  #include <time.h>
> +
> +#include "igt.h"
>  #include "igt_device.h"
>  #include "igt_device_scan.h"
>  
> 





  reply	other threads:[~2024-08-22 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21  9:51 [PATCH i-g-t v1 0/1] Fix compilation for musl in intel/kms_pm_backlight Kamil Konieczny
2024-08-21  9:51 ` [PATCH i-g-t v1 1/1] tests/intel/kms_pm_backlight: Fixed build on musl Kamil Konieczny
2024-08-22 18:44   ` Janusz Krzysztofik [this message]
2024-08-23  9:41     ` Kamil Konieczny
2024-08-21 14:56 ` ✓ CI.xeBAT: success for Fix compilation for musl in intel/kms_pm_backlight Patchwork
2024-08-21 15:02 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-21 16:35 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-21 17:13   ` Kamil Konieczny
2024-08-21 17:48 ` ✗ Fi.CI.IGT: " Patchwork
2024-08-23  9:36   ` Kamil Konieczny

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=3305001.aeNJFYEL58@jkrzyszt-mobl2.ger.corp.intel.com \
    --to=janusz.krzysztofik@linux.intel.com \
    --cc=bernd@kuhls.net \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=st3r4g@protonmail.com \
    --cc=triallax@tutanota.com \
    --cc=xbjfk.github@gmail.com \
    --cc=yuka@yuka.dev \
    /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