From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: peterz@infradead.org
Cc: mingo@redhat.com, will@kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] locking/rwsem: remove redundant semicolon of down_write_nest_lock
Date: Wed, 12 Aug 2020 10:36:14 +0200 [thread overview]
Message-ID: <8356e96d-8732-0e2e-e962-dec671c19eb2@gmail.com> (raw)
In-Reply-To: <20200812081057.GJ2674@hirez.programming.kicks-ass.net>
Am 12.08.20 um 10:10 schrieb peterz@infradead.org:
> On Tue, Aug 11, 2020 at 01:18:52PM +0200, Christian König wrote:
>> From: Guchun Chen <guchun.chen@amd.com>
>>
>> Otherwise, braces are needed when using it.
>>
>> Signed-off-by: Guchun Chen <guchun.chen@amd.com>
>> Reviewed-by: Christian König <christian.koenig@amd.com>
> Thanks!
Do you pick it up or can I push it through drm-misc-fixes?
If the former please let me know when it hits Linus tree since I have a
driver which contains some extra {} because of this.
Thanks,
Christian.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: peterz@infradead.org
Cc: mingo@redhat.com, will@kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] locking/rwsem: remove redundant semicolon of down_write_nest_lock
Date: Wed, 12 Aug 2020 10:36:14 +0200 [thread overview]
Message-ID: <8356e96d-8732-0e2e-e962-dec671c19eb2@gmail.com> (raw)
In-Reply-To: <20200812081057.GJ2674@hirez.programming.kicks-ass.net>
Am 12.08.20 um 10:10 schrieb peterz@infradead.org:
> On Tue, Aug 11, 2020 at 01:18:52PM +0200, Christian König wrote:
>> From: Guchun Chen <guchun.chen@amd.com>
>>
>> Otherwise, braces are needed when using it.
>>
>> Signed-off-by: Guchun Chen <guchun.chen@amd.com>
>> Reviewed-by: Christian König <christian.koenig@amd.com>
> Thanks!
Do you pick it up or can I push it through drm-misc-fixes?
If the former please let me know when it hits Linus tree since I have a
driver which contains some extra {} because of this.
Thanks,
Christian.
next prev parent reply other threads:[~2020-08-12 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 11:18 [PATCH] locking/rwsem: remove redundant semicolon of down_write_nest_lock Christian König
2020-08-11 11:18 ` Christian König
2020-08-12 8:10 ` peterz
2020-08-12 8:10 ` peterz
2020-08-12 8:36 ` Christian König [this message]
2020-08-12 8:36 ` Christian König
2020-08-12 10:36 ` peterz
2020-08-12 10:36 ` peterz
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=8356e96d-8732-0e2e-e962-dec671c19eb2@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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.