Hi Ville,

On 11/03/2019 16:00, Ville Syrjälä wrote:
> On Mon, Mar 11, 2019 at 03:36:39PM +0000, Kieran Bingham wrote:
>> Trivial fixes identified while working on the DRM code.
>>
>>   s/artifically/artificially/
>>   s/achive/acheive/
> 
> achieve?

Good point :) It's rubbish being a native English speaker :( - So much
harder to get the spelling correct :D.

I'll repost a v2 - sorry for the noise!

--
Kieran



> 
>>
>> Signed-off-by: Kieran Bingham <kieran.bingham+rene...@ideasonboard.com>
>> ---
>>  drivers/gpu/drm/drm_atomic_helper.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_atomic_helper.c 
>> b/drivers/gpu/drm/drm_atomic_helper.c
>> index 540a77a2ade9..ccb278ed1bf8 100644
>> --- a/drivers/gpu/drm/drm_atomic_helper.c
>> +++ b/drivers/gpu/drm/drm_atomic_helper.c
>> @@ -1752,7 +1752,7 @@ int drm_atomic_helper_commit(struct drm_device *dev,
>>       *
>>       * NOTE: Commit work has multiple phases, first hardware commit, then
>>       * cleanup. We want them to overlap, hence need system_unbound_wq to
>> -     * make sure work items don't artifically stall on each another.
>> +     * make sure work items don't artificially stall on each another.
>>       */
>>  
>>      drm_atomic_state_get(state);
>> @@ -1786,7 +1786,7 @@ EXPORT_SYMBOL(drm_atomic_helper_commit);
>>   *
>>   * Asynchronous workers need to have sufficient parallelism to be able to 
>> run
>>   * different atomic commits on different CRTCs in parallel. The simplest 
>> way to
>> - * achive this is by running them on the &system_unbound_wq work queue. Note
>> + * acheive this is by running them on the &system_unbound_wq work queue. 
>> Note
>>   * that drivers are not required to split up atomic commits and run an
>>   * individual commit in parallel - userspace is supposed to do that if it 
>> cares.
>>   * But it might be beneficial to do that for modesets, since those 
>> necessarily
>> -- 
>> 2.19.1
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Reply via email to