All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Javier Martinez Canillas <javierm@redhat.com>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Mark Brown <broonie@kernel.org>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Markus Elfring <Markus.Elfring@web.de>
Subject: Re: [PATCH v5 2/3] treewide: Remove dev_err() usage after platform_get_irq()
Date: Tue, 30 Jul 2019 17:51:48 +0200	[thread overview]
Message-ID: <20190730155148.GA21985@kroah.com> (raw)
In-Reply-To: <5d4063e0.1c69fb81.fb7c2.9528@mx.google.com>

On Tue, Jul 30, 2019 at 08:35:59AM -0700, Stephen Boyd wrote:
> Quoting Greg Kroah-Hartman (2019-07-29 23:49:17)
> > On Mon, Jul 29, 2019 at 10:38:44PM -0700, Stephen Boyd wrote:
> > > We don't need dev_err() messages when platform_get_irq() fails now that
> > > platform_get_irq() prints an error message itself when something goes
> > > wrong. Let's remove these prints with a simple semantic patch.
> > > 
> > > // <smpl>
> > > @@
> > > expression ret;
> > > struct platform_device *E;
> > > @@
> > > 
> > > ret =
> > > (
> > > platform_get_irq(E, ...)
> > > |
> > > platform_get_irq_byname(E, ...)
> > > );
> > > 
> > > if ( \( ret < 0 \| ret <= 0 \) )
> > > {
> > > (
> > > -if (ret != -EPROBE_DEFER)
> > > -{ ...
> > > -dev_err(...);
> > > -... }
> > > |
> > > ...
> > > -dev_err(...);
> > > )
> > > ...
> > > }
> > > // </smpl>
> > > 
> > > While we're here, remove braces on if statements that only have one
> > > statement (manually).
> > 
> > I like this, and I like patch 1/3, but this is going to conflict like
> > crazy all over the tree with who ever ends up taking it in their tree.
> > 
> > Can you just break this up into per-subsystem pieces and send it through
> > those trees, and any remaining ones I can take, but at least give
> > maintainers a chance to take it.
> 
> Ok. Let me resend just this patch broken up into many pieces.

Thanks.

> > You are also going to have to do a sweep every other release or so to
> > catch the stragglers.
> 
> I was going to let the janitors do that.

We are all janitors :)

  reply	other threads:[~2019-07-30 15:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30  5:38 [PATCH v5 0/3] Add error message to platform_get_irq*() Stephen Boyd
2019-07-30  5:38 ` [Cocci] " Stephen Boyd
2019-07-30  5:38 ` [PATCH v5 1/3] driver core: platform: Add an " Stephen Boyd
2019-07-30  9:44   ` Markus Elfring
2019-07-30  9:44     ` Markus Elfring
2019-07-30 12:30   ` Markus Elfring
2019-07-30 12:30     ` Markus Elfring
2019-07-30  5:38 ` [PATCH v5 2/3] treewide: Remove dev_err() usage after platform_get_irq() Stephen Boyd
2019-07-30  6:49   ` Greg Kroah-Hartman
2019-07-30 15:35     ` Stephen Boyd
2019-07-30 15:51       ` Greg Kroah-Hartman [this message]
2019-07-30 17:16       ` Andy Shevchenko
2019-07-30 17:17         ` Andy Shevchenko
2019-07-30 17:21           ` Stephen Boyd
2019-07-30 17:31             ` Andy Shevchenko
2019-07-30 10:00   ` [v5 " Markus Elfring
2019-07-30 10:00     ` Markus Elfring
2019-07-30 10:00   ` Markus Elfring
2019-07-30 10:00     ` Markus Elfring
2019-07-30  5:38 ` [PATCH v5 3/3] coccinelle: Add script to check for platform_get_irq() excessive prints Stephen Boyd
2019-07-30  5:38   ` [Cocci] " Stephen Boyd
2019-07-30  8:49   ` Markus Elfring
2019-07-30  8:49     ` [Cocci] " Markus Elfring
2019-07-30  8:49     ` Markus Elfring
2019-07-31 14:26 ` [Cocci] [PATCH v5 0/3] Add error message to platform_get_irq*() Wolfram Sang
2019-07-31 14:26   ` Wolfram Sang
2019-07-31 14:52   ` Stephen Boyd
2019-07-31 14:52     ` Stephen Boyd
2019-08-01 12:25     ` Wolfram Sang
2019-08-01 12:25       ` Wolfram Sang
2019-08-08  7:51       ` Geert Uytterhoeven
2019-08-08  7:51         ` Geert Uytterhoeven

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=20190730155148.GA21985@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Markus.Elfring@web.de \
    --cc=a.hajda@samsung.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=broonie@kernel.org \
    --cc=javierm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robh@kernel.org \
    --cc=swboyd@chromium.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.