Message ID | 20171101140436.2743-1-Liviu.Dudau@arm.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Wed, Nov 1, 2017 at 10:04 AM, Liviu Dudau <Liviu.Dudau@arm.com> wrote: > Minor spelling fix for 'monster' and replace 'on' with 'own' in > comments. > > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com> Reviewed-by: Alex Deucher <alexander.deucher@amd.com> > --- > drivers/gpu/drm/drm_atomic.c | 2 +- > drivers/gpu/drm/drm_mm.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c > index c2da5585e2012..11614ea03fc8b 100644 > --- a/drivers/gpu/drm/drm_atomic.c > +++ b/drivers/gpu/drm/drm_atomic.c > @@ -1808,7 +1808,7 @@ int drm_atomic_debugfs_init(struct drm_minor *minor) > #endif > > /* > - * The big monstor ioctl > + * The big monster ioctl > */ > > static struct drm_pending_vblank_event *create_vblank_event( > diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c > index 61a1c8ea74bc5..eb86bc3f753b3 100644 > --- a/drivers/gpu/drm/drm_mm.c > +++ b/drivers/gpu/drm/drm_mm.c > @@ -92,7 +92,7 @@ > * some basic allocator dumpers for debugging. > * > * Note that this range allocator is not thread-safe, drivers need to protect > - * modifications with their on locking. The idea behind this is that for a full > + * modifications with their own locking. The idea behind this is that for a full > * memory manager additional data needs to be protected anyway, hence internal > * locking would be fully redundant. > */ > -- > 2.14.3 > > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Liviu, 2017-11-01 Liviu Dudau <Liviu.Dudau@arm.com>: > Minor spelling fix for 'monster' and replace 'on' with 'own' in > comments. > > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com> > --- > drivers/gpu/drm/drm_atomic.c | 2 +- > drivers/gpu/drm/drm_mm.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) pushed to drm-misc-next. Thanks for your patch. Gustavo
On Thu, Nov 02, 2017 at 11:12:08AM -0200, Gustavo Padovan wrote: > Hi Liviu, Hi Gustavo, > > 2017-11-01 Liviu Dudau <Liviu.Dudau@arm.com>: > > > Minor spelling fix for 'monster' and replace 'on' with 'own' in > > comments. > > > > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com> > > --- > > drivers/gpu/drm/drm_atomic.c | 2 +- > > drivers/gpu/drm/drm_mm.c | 2 +- > > 2 files changed, 2 insertions(+), 2 deletions(-) > > pushed to drm-misc-next. Thanks for your patch. Thank you for pulling all the other patches as well. Best regards, Liviu > > Gustavo
diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c index c2da5585e2012..11614ea03fc8b 100644 --- a/drivers/gpu/drm/drm_atomic.c +++ b/drivers/gpu/drm/drm_atomic.c @@ -1808,7 +1808,7 @@ int drm_atomic_debugfs_init(struct drm_minor *minor) #endif /* - * The big monstor ioctl + * The big monster ioctl */ static struct drm_pending_vblank_event *create_vblank_event( diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c index 61a1c8ea74bc5..eb86bc3f753b3 100644 --- a/drivers/gpu/drm/drm_mm.c +++ b/drivers/gpu/drm/drm_mm.c @@ -92,7 +92,7 @@ * some basic allocator dumpers for debugging. * * Note that this range allocator is not thread-safe, drivers need to protect - * modifications with their on locking. The idea behind this is that for a full + * modifications with their own locking. The idea behind this is that for a full * memory manager additional data needs to be protected anyway, hence internal * locking would be fully redundant. */
Minor spelling fix for 'monster' and replace 'on' with 'own' in comments. Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com> --- drivers/gpu/drm/drm_atomic.c | 2 +- drivers/gpu/drm/drm_mm.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)