linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
	Dejin Zheng <zhengdejin5@gmail.com>,
	linux-i2c <linux-i2c@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Thor Thayer <thor.thayer@linux.intel.com>,
	Tang Bin <tangbin@cmss.chinamobile.com>,
	Stephen Boyd <swboyd@chromium.org>,
	Patrick Williams <alpawi@amazon.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Krzysztof Adamski <krzysztof.adamski@nokia.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Barry Song <baohua@kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Dong Aisheng <aisheng.dong@nxp.com>,
	George Cherian <gcherian@marvell.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH v2] i2c: busses: remove duplicate dev_err()
Date: Fri, 17 Apr 2020 00:29:20 +0300	[thread overview]
Message-ID: <CAHp75Vdd8SzrzXuxTTtkqRBWZuebhumJfv_fBPqdKwe780_ZEQ@mail.gmail.com> (raw)
In-Reply-To: <7713a931e4475294de85b74aca298dde8be4242d.camel@perches.com>

On Fri, Apr 17, 2020 at 12:28 AM Joe Perches <joe@perches.com> wrote:
>
> On Thu, 2020-04-16 at 20:22 +0200, Markus Elfring wrote:
> > > it will print an error message by itself when platform_get_irq()
> > > goes wrong. so don't need dev_err() in here again.
> >
> > I suggest to improve the commit message considerably.
>
> I suggest you ignore Markus' suggestion.
>
> The commit message is OK.
>
> The subject _could_ have included "platform_get_irq" something like
>
> Subject: [PATCH v2] i2c: busses: Remove platform_get_irq()'s duplicated dev_err()
>
> but I believe it's not important enough to redo.

+1, I think it's good enough.

-- 
With Best Regards,
Andy Shevchenko

  parent reply	other threads:[~2020-04-16 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 15:23 [PATCH v2] i2c: busses: remove duplicate dev_err() Dejin Zheng
2020-04-16 15:50 ` Andy Shevchenko
2020-04-16 18:22 ` Markus Elfring
2020-04-16 19:34   ` Joe Perches
2020-04-16 20:30     ` [v2] " Markus Elfring
2020-04-16 21:29     ` Andy Shevchenko [this message]
2020-04-18 21:44 ` [PATCH v2] " Wolfram Sang

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=CAHp75Vdd8SzrzXuxTTtkqRBWZuebhumJfv_fBPqdKwe780_ZEQ@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=Markus.Elfring@web.de \
    --cc=aisheng.dong@nxp.com \
    --cc=alpawi@amazon.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=ardb@kernel.org \
    --cc=baohua@kernel.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=gcherian@marvell.com \
    --cc=hdegoede@redhat.com \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=krzysztof.adamski@nokia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=narmstrong@baylibre.com \
    --cc=swboyd@chromium.org \
    --cc=tangbin@cmss.chinamobile.com \
    --cc=thor.thayer@linux.intel.com \
    --cc=vigneshr@ti.com \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=zhengdejin5@gmail.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).