mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>,
	Wen Yang <wen.yang99@zte.com.cn>,
	kernel-janitors@vger.kernel.org
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Cheng Shengyu <cheng.shengyu@zte.com.cn>,
	Kumar Gala <galak@kernel.crashing.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Paul Mackerras <paulus@samba.org>, Scott Wood <oss@buserror.net>,
	Xue Zhihong <xue.zhihong@zte.com.cn>,
	Yi Wang <wang.yi59@zte.com.cn>,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-pm@vger.kernel.org
Subject: Re: Coccinelle: Checking of_node_put() calls with SmPL
Date: Thu, 11 Jul 2019 11:33:30 +0200	[thread overview]
Message-ID: <e0e19253-afbc-3576-fcc3-22deea4db674@web.de> (raw)
In-Reply-To: <alpine.DEB.2.20.1907110845551.3626@hadrien>

> In my experience, when you start looking at these of_node_put things,
> all sorts of strange things appear...

How much will this situation influence the achievement of further improvements
also for your software?

Regards,
Markus

  reply	other threads:[~2019-07-11  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201907111435459627761@zte.com.cn>
2019-07-11  6:46 ` Julia Lawall
2019-07-11  9:33   ` Markus Elfring [this message]
2019-07-11  9:04 ` Markus Elfring
2019-07-11 14:41 ` Tyrel Datwyler
     [not found] <201907101533443009168@zte.com.cn>
2019-07-10 15:15 ` Markus Elfring

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=e0e19253-afbc-3576-fcc3-22deea4db674@web.de \
    --to=markus.elfring@web.de \
    --cc=benh@kernel.crashing.org \
    --cc=cheng.shengyu@zte.com.cn \
    --cc=daniel.lezcano@linaro.org \
    --cc=galak@kernel.crashing.org \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=oss@buserror.net \
    --cc=paulus@samba.org \
    --cc=rjw@rjwysocki.net \
    --cc=wang.yi59@zte.com.cn \
    --cc=wen.yang99@zte.com.cn \
    --cc=xue.zhihong@zte.com.cn \
    /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

all inboxes | Powered by JetHome®