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
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
