From: Julien Grall <julien.grall@arm.com>
To: Hanjun Guo <hanjun.guo@linaro.org>, kvmarm@lists.cs.columbia.edu
Cc: christoffer.dall@linaro.org, marc.zyngier@arm.com,
fu.wei@linaro.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, wei@redhat.com,
al.stone@linaro.org, gg@slimlogic.co.uk
Subject: Re: [PATCH v6 05/10] irqchip/gic-v3: Prefix all pr_* messages by "GICv3: "
Date: Tue, 26 Apr 2016 18:52:00 +0100 [thread overview]
Message-ID: <571FAAC0.3070706@arm.com> (raw)
In-Reply-To: <570E190C.8020203@linaro.org>
Hi Hanjun,
Sorry for the late answer.
On 13/04/16 11:01, Hanjun Guo wrote:
> On 2016/4/11 23:32, Julien Grall wrote:
>> Currently, most of the pr_* messages in the GICv3 driver don't have a
>> prefix. Add one to make clear where the messages come from.
>>
>> Signed-off-by: Julien Grall <julien.grall@arm.com>
>>
>> ---
>> Changes in v6:
>> - Patch added
>> ---
>> drivers/irqchip/irq-gic-v3.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
>> index 5b7d3c2..6dc6f03 100644
>> --- a/drivers/irqchip/irq-gic-v3.c
>> +++ b/drivers/irqchip/irq-gic-v3.c
>> @@ -15,6 +15,8 @@
>> * along with this program. If not, see
>> <http://www.gnu.org/licenses/>.
>> */
>>
>> +#define pr_fmt(fmt) "GICv3: " fmt
>
> I don't think this patch is needed, as GICv3 and GICv2 will
> not be probed at the same time, did I miss something?
True, however this make slightly easier to know which driver is in-use
and avoid to prefix all the messages with "GIC:" or "GICv3:".
>
> Further more, there are prefixes in pr_fmt in this
> patch using GIC:, with your patch added, it will print:
>
> GIV3: GIC: .....
>
> which is not a good idea.
I think it is better than having message without prefix at all.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2016-04-26 17:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 15:32 [PATCH v6 00/10] arm64: Add support for KVM with ACPI Julien Grall
2016-04-11 15:32 ` [PATCH v6 01/10] clocksource: arm_arch_timer: Gather KVM specific information in a structure Julien Grall
2016-04-12 5:43 ` Daniel Lezcano
2016-04-24 2:54 ` Shanker Donthineni
2016-04-11 15:32 ` [PATCH v6 02/10] clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ Julien Grall
2016-04-12 5:44 ` Daniel Lezcano
2016-04-24 2:57 ` Shanker Donthineni
2016-04-11 15:32 ` [PATCH v6 03/10] irqchip/gic-v2: Gather ACPI specific data in a single structure Julien Grall
2016-04-24 2:58 ` Shanker Donthineni
2016-04-11 15:32 ` [PATCH v6 04/10] irqchip/gic-v2: Parse and export virtual GIC information Julien Grall
2016-04-13 9:50 ` Hanjun Guo
2016-04-24 3:00 ` Shanker Donthineni
2016-04-11 15:32 ` [PATCH v6 05/10] irqchip/gic-v3: Prefix all pr_* messages by "GICv3: " Julien Grall
2016-04-13 10:01 ` Hanjun Guo
2016-04-26 17:52 ` Julien Grall [this message]
2016-04-11 15:32 ` [PATCH v6 06/10] irqchip/gic-v3: Gather all ACPI specific data in a single structure Julien Grall
2016-04-24 3:02 ` Shanker Donthineni
2016-04-11 15:32 ` [PATCH v6 07/10] irqchip/gic-v3: Parse and export virtual GIC information Julien Grall
2016-04-24 3:05 ` Shanker Donthineni
2016-04-11 15:32 ` [PATCH v6 08/10] KVM: arm/arm64: arch_timer: Rely on the arch timer to parse the firmware tables Julien Grall
2016-04-24 3:06 ` Shanker Donthineni
2016-04-11 15:32 ` [PATCH v6 09/10] KVM: arm/arm64: vgic: Rely on the GIC driver " Julien Grall
2016-04-24 3:32 ` Shanker Donthineni
2016-04-11 15:33 ` [PATCH v6 10/10] clocksource: arm_arch_timer: Remove arch_timer_get_timecounter Julien Grall
2016-04-12 5:44 ` Daniel Lezcano
2016-04-12 12:15 ` Christoffer Dall
2016-04-12 12:49 ` Daniel Lezcano
2016-04-24 3:33 ` Shanker Donthineni
2016-04-28 13:13 ` [PATCH v6 00/10] arm64: Add support for KVM with ACPI Marc Zyngier
2016-05-02 12:54 ` Jason Cooper
2016-05-03 8:21 ` Christoffer Dall
2016-05-03 12:46 ` Jason Cooper
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=571FAAC0.3070706@arm.com \
--to=julien.grall@arm.com \
--cc=al.stone@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=fu.wei@linaro.org \
--cc=gg@slimlogic.co.uk \
--cc=hanjun.guo@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=wei@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).