From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/2] scripts/generate_clear_kernel: Improve usage instructions.
Date: Mon, 15 Jun 2020 11:54:50 -0700 [thread overview]
Message-ID: <20200615185450.GB334084@intel.com> (raw)
In-Reply-To: <20200611093502.GM9497@platvala-desk.ger.corp.intel.com>
On Thu, Jun 11, 2020 at 12:35:02PM +0300, Petri Latvala wrote:
> On Wed, Jun 10, 2020 at 08:44:34PM -0700, Rodrigo Vivi wrote:
> > Fix the script name and make the path to mesa i915_asm a bit
> > more clear
> >
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> For the series:
>
> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
thanks, pushed
>
>
>
> > ---
> > scripts/generate_clear_kernel.sh | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/scripts/generate_clear_kernel.sh b/scripts/generate_clear_kernel.sh
> > index af628a86..90bbdf5d 100755
> > --- a/scripts/generate_clear_kernel.sh
> > +++ b/scripts/generate_clear_kernel.sh
> > @@ -26,7 +26,7 @@
> > export ASSEMBLY_SOURCE=./lib/i915/shaders/clear_kernel
> >
> > function get_help {
> > - echo "Usage: asm_eu_kernel.sh [options]"
> > + echo "Usage: ${0} [options]"
> > echo "Note: hsw_clear_kernel.c/ivb_clear_kernel.c automatically generated by this script should never be modified - it would be imported to i915, to use as it is..."
> > echo " "
> > echo "Please make sure your Mesa tool is compiled with "-Dtools=intel" and "-Ddri-drivers=i965", and run this script from IGT source root directory"
> > @@ -37,7 +37,7 @@ function get_help {
> > echo " -o=name_of_file output file to store Mesa assembled c-literal for the device - If none specified, default file will be used - ivb/hsw-cb_assembled"
> > echo " -m=mesa Path to Mesa i965_asm binary"
> > echo " "
> > - echo " Usage example: \"scripts/generate_clear_kernel.sh -g hsw -o hsw_clear_buffer.h -m /path/to/Mesa/i965_asm/binary\""
> > + echo " Usage example: \"./scripts/generate_clear_kernel.sh -g hsw -o hsw_clear_buffer.h -m ~/mesa/build/src/intel/tools/i965_asm\""
> > }
> >
> > function include_array # $1=array_name - update Mesa output with desired format
> > --
> > 2.24.1
> >
> > _______________________________________________
> > igt-dev mailing list
> > igt-dev@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-06-15 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 3:44 [igt-dev] [PATCH i-g-t 1/2] scripts/generate_clear_kernel: Improve usage instructions Rodrigo Vivi
2020-06-11 3:44 ` [igt-dev] [PATCH i-g-t 2/2] scripts/generate_clear_kernel: Clean up header license/copyright Rodrigo Vivi
2020-06-11 5:20 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] scripts/generate_clear_kernel: Improve usage instructions Patchwork
2020-06-11 9:35 ` [igt-dev] [PATCH i-g-t 1/2] " Petri Latvala
2020-06-15 18:54 ` Rodrigo Vivi [this message]
2020-06-11 12:11 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2] " 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=20200615185450.GB334084@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@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