From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Liang He <windhl@126.com>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: soc: sifive: Add missing of_node_put() in sifive_l2_cache.c
Date: Thu, 16 Jun 2022 20:45:26 +0200 [thread overview]
Message-ID: <1285751d-c4af-23ec-148c-88b0e3867e6a@wanadoo.fr> (raw)
In-Reply-To: <7321db1e.3902.1816b00e5e6.Coremail.windhl@126.com>
Le 16/06/2022 à 07:33, Liang He a écrit :
>
> Sorry for my troubles. I will check my patch more carefully.
No problem, you seem to be knew on the lists so you have to learn the
tricks, coding-style, tools...
Happy patching :)
CJ
WARNING: multiple messages have this Message-ID (diff)
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Liang He <windhl@126.com>
Cc: palmer@dabbelt.com, paul.walmsley@sifive.com,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: soc: sifive: Add missing of_node_put() in sifive_l2_cache.c
Date: Thu, 16 Jun 2022 20:45:26 +0200 [thread overview]
Message-ID: <1285751d-c4af-23ec-148c-88b0e3867e6a@wanadoo.fr> (raw)
In-Reply-To: <7321db1e.3902.1816b00e5e6.Coremail.windhl@126.com>
Le 16/06/2022 à 07:33, Liang He a écrit :
>
> Sorry for my troubles. I will check my patch more carefully.
No problem, you seem to be knew on the lists so you have to learn the
tricks, coding-style, tools...
Happy patching :)
CJ
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-06-16 18:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 12:23 [PATCH] drivers: soc: sifive: Add missing of_node_put() in sifive_l2_cache.c Liang He
2022-06-15 12:23 ` Liang He
2022-06-15 21:58 ` kernel test robot
2022-06-15 21:58 ` kernel test robot
2022-06-16 4:54 ` Liang He
2022-06-16 4:54 ` Liang He
2022-06-16 4:54 ` Liang He
2022-06-16 5:12 ` Christophe JAILLET
2022-06-16 5:12 ` Christophe JAILLET
2022-06-16 5:33 ` Liang He
2022-06-16 5:33 ` Liang He
2022-06-16 18:45 ` Christophe JAILLET [this message]
2022-06-16 18:45 ` Christophe JAILLET
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=1285751d-c4af-23ec-148c-88b0e3867e6a@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=windhl@126.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 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.