All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Harrison, John C" <john.c.harrison@intel.com>
Subject: Re: [PATCH] drm/i915/gt/uc: Fix typo in comment
Date: Fri, 14 Jun 2024 15:45:40 -0400	[thread overview]
Message-ID: <Zmyd5O5LJU-RvcUD@intel.com> (raw)
In-Reply-To: <CH0PR11MB54440CF4CB01809F00A1B0D4E5C22@CH0PR11MB5444.namprd11.prod.outlook.com>

On Fri, Jun 14, 2024 at 03:23:54PM +0000, Cavitt, Jonathan wrote:
> -----Original Message-----
> From: Andi Shyti <andi.shyti@linux.intel.com> 
> Sent: Friday, June 14, 2024 8:22 AM
> To: Andi Shyti <andi.shyti@linux.intel.com>
> Cc: intel-gfx <intel-gfx@lists.freedesktop.org>; dri-devel <dri-devel@lists.freedesktop.org>; Harrison, John C <john.c.harrison@intel.com>; Cavitt, Jonathan <jonathan.cavitt@intel.com>
> Subject: Re: [PATCH] drm/i915/gt/uc: Fix typo in comment
> > 
> > I guess sparse and potential CI errors won't minimally relate to
> > this patch.
> 
> Yeah, I don't see how a change to a comment could ever be related
> to any CI errors:
> 
> Reviewed-by: Jonathan Cavitt

Please ensure you use the full line.
1. People don't have to go to the header of your email to get your email.
2. People might not be entirely sure of your choice of email. Please notice that
even on Intel many folks have @intel.com and @linux.intel.com and sometimes although
responding from one, they use the other to sign things.
3. Tooling! (b4, patchwork, etc) There are many tools that get these tags directly
 from the email response and by using partial one you can complicate things.

If you also allow one advice, try to use a terminal mail client like mutt and
open the replies in your favorite editor and add macros there to add your lines
based on shortcuts... For instance, on my case I use mutt+emacs and I just hit
Ctrl+c-rev and that adds my full rv-b tag in the response.

Thanks,
Rodrigo.

> -Jonathan Cavitt
> 
> > 
> > Adding also Jonathan in Cc :-)
> > 
> > Thanks,	
> > Andi
> > 
> > On Fri, Jun 14, 2024 at 12:28:37AM +0200, Andi Shyti wrote:
> > > Replace "dynmically" with "dynamically".
> > > 
> > > Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> > > Cc: John Harrison <John.C.Harrison@Intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h b/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> > > index 14797e80bc92..263c9c3f6a03 100644
> > > --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> > > +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h
> > > @@ -295,7 +295,7 @@ struct guc_update_scheduling_policy_header {
> > >  } __packed;
> > >  
> > >  /*
> > > - * Can't dynmically allocate memory for the scheduling policy KLV because
> > > + * Can't dynamically allocate memory for the scheduling policy KLV because
> > >   * it will be sent from within the reset path. Need a fixed size lump on
> > >   * the stack instead :(.
> > >   *
> > > -- 
> > > 2.45.1
> > 

  reply	other threads:[~2024-06-14 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 22:28 [PATCH] drm/i915/gt/uc: Fix typo in comment Andi Shyti
2024-06-13 23:26 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-06-13 23:34 ` ✓ Fi.CI.BAT: success " Patchwork
2024-06-14 15:21 ` [PATCH] " Andi Shyti
2024-06-14 15:23   ` Cavitt, Jonathan
2024-06-14 19:45     ` Rodrigo Vivi [this message]
2024-06-14 20:21       ` Cavitt, Jonathan
2024-06-15  6:59 ` ✓ Fi.CI.IGT: success 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=Zmyd5O5LJU-RvcUD@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --cc=jonathan.cavitt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.