Re: [PATCH] drm/display: drop unexpected word "the" in the comments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yeah I'm not totally sure what's going on here, I wouldn't worry about it too much. I will just push the patches manually

On Wed, 2022-06-22 at 03:01 +0800, 蒋健 wrote:
I got the list as follow:
 ~/linux-kernel/linux-next  on master ⇡1  ./scripts/get_maintainer.pl 0001-drm-display-Remove-duplicate-the-in-two-places.patch
David Airlie <airlied@xxxxxxxx> (maintainer:DRM DRIVERS)
Daniel Vetter <daniel@xxxxxxxx> (maintainer:DRM DRIVERS)
Jani Nikula <jani.nikula@xxxxxxxxx> (commit_signer:8/21=38%,authored:5/21=24%)
Lyude Paul <lyude@xxxxxxxxxx> (commit_signer:7/21=33%,authored:2/21=10%)
Thomas Zimmermann <tzimmermann@xxxxxxx> (commit_signer:5/21=24%,authored:5/21=24%)
Douglas Anderson <dianders@xxxxxxxxxxxx> (commit_signer:5/21=24%,authored:3/21=14%)
"Ville Syrjälä" <ville.syrjala@xxxxxxxxxxxxxxx> (commit_signer:5/21=24%)
Imre Deak <imre.deak@xxxxxxxxx> (authored:2/21=10%)
dri-devel@xxxxxxxxxxxxxxxxxxxxx (open list:DRM DRIVERS)
linux-kernel@xxxxxxxxxxxxxxx (open list)

Submit patch CMD as follow:
"git send-email 0001-drm-display-Remove-duplicate-the-in-two-places.patch --to airlied@xxxxxxxx,daniel@xxxxxxxx --cc jani.nikula@xxxxxxxxx,lyude@xxxxxxxxxx,tzimmermann@xxxxxxx,dianders@xxxxxxxxxxxx,ville.syrjala@xxxxxxxxxxxxxxx,imre.deak@xxxxxxxxx,dri-devel@xxxxxxxxxxxxxxxxxxxxx,linux-kernel@xxxxxxxxxxxxxxx "

 
------------------ Original ------------------
Date:  Wed, Jun 22, 2022 02:47 AM
To:  "Lyude Paul"<lyude@xxxxxxxxxx>; "airlied"<airlied@xxxxxxxx>; "daniel"<daniel@xxxxxxxx>;
Cc:  "jani.nikula"<jani.nikula@xxxxxxxxx>; "ville.syrjala"<ville.syrjala@xxxxxxxxxxxxxxx>; "tzimmermann"<tzimmermann@xxxxxxx>; "dianders"<dianders@xxxxxxxxxxxx>; "imre.deak"<imre.deak@xxxxxxxxx>; "dri-devel"<dri-devel@xxxxxxxxxxxxxxxxxxxxx>;
Subject:  Re: [PATCH] drm/display: drop unexpected word "the" in the comments
 
Okay,I will submit a new patch immediately.

On Wed,Jun 22,2022 2:41 AM Lyude Paul <lyude@xxxxxxxxxx> wrote:
You can send it by adding email addresses to git send-email with the "--to foo@xxxxxxx" argument. If it doesn't come up on patchwork the second try don't worry about it, I'll look and see if I can workaround it. TBH I'm not entirely sure why it didn't show up in the first place

On Wed, 2022-06-22 at 02:38 +0800, 蒋健 wrote:
I need resubmit a new patch,  how can i make sure dri-devel@  is explicitly?I got to:list by the script
 name of get_maintainer.pl.
Pls help me…

On Wed,Jun 22,2022 2:07 AM Lyude Paul <lyude@xxxxxxxxxx> wrote:
Actually I hate to ask but could you resend this and the other patch that you
sent and make sure that dri-devel@ is explicitly in the to: list? For some
reason these patches don't seem to be coming up on patchwork

On Tue, 2022-06-21 at 13:54 -0400, Lyude Paul wrote:
> Reviewed-by: Lyude Paul <lyude@xxxxxxxxxx>
>
> Will push to the appropriate branch in a moment
>
> On Tue, 2022-06-21 at 21:14 +0800, Jiang Jian wrote:
> > there is an unexpected word "the" in the comments that need to be dropped
> >
> > file: drivers/gpu/drm/display/drm_dp_helper.c
> > line: 1600
> >   * Doesn't account the the "MOT" bit, and instead assumes each
> > changed to
> >   * Doesn't account the "MOT" bit, and instead assumes each
> >
> > Signed-off-by: Jiang Jian <jiangjian@xxxxxxxxxx>
> > ---
> >  drivers/gpu/drm/display/drm_dp_helper.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/display/drm_dp_helper.c
> > b/drivers/gpu/drm/display/drm_dp_helper.c
> > index e7c22c2ca90c..499f75768523 100644
> > --- a/drivers/gpu/drm/display/drm_dp_helper.c
> > +++ b/drivers/gpu/drm/display/drm_dp_helper.c
> > @@ -1597,7 +1597,7 @@ static int drm_dp_aux_reply_duration(const struct
> > drm_dp_aux_msg *msg)
> >   * Calculate the length of the i2c transfer in usec, assuming
> >   * the i2c bus speed is as specified. Gives the the "worst"
> >   * case estimate, ie. successful while as long as possible.
> > - * Doesn't account the the "MOT" bit, and instead assumes each
> > + * Doesn't account the "MOT" bit, and instead assumes each
> >   * message includes a START, ADDRESS and STOP. Neither does it
> >   * account for additional random variables such as clock stretching.
> >   */
>


-- 
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux