linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: "Markus Elfring" <Markus.Elfring@web.de>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Thierry Reding" <treding@nvidia.com>,
	linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v8 29/32] i2c: tegra: Clean up printk messages
Date: Wed, 23 Sep 2020 19:10:24 +0300	[thread overview]
Message-ID: <5e5d4592-7ff4-2de2-eff1-ad5e006861b0@gmail.com> (raw)
In-Reply-To: <550a2820-e3bd-7752-f86e-74598def8c62@web.de>

23.09.2020 14:43, Markus Elfring пишет:
>> This patch unifies style of all messages in the driver by starting them
>> with a lowercase letter and using consistent capitalization and wording
>> for all messages.
> 
> * Does this change description express a contradiction?

no

> * How does the proposed deletion of two error messages fit to such information?

If you'll read the code carefully, then you may notice that they are not
removed, but squashed and moved out to tegra_i2c_dma_submit().

       reply	other threads:[~2020-09-23 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <550a2820-e3bd-7752-f86e-74598def8c62@web.de>
2020-09-23 16:10 ` Dmitry Osipenko [this message]
2020-09-22 22:51 [PATCH v8 00/32] Improvements for Tegra I2C driver Dmitry Osipenko
2020-09-22 22:51 ` [PATCH v8 29/32] i2c: tegra: Clean up printk messages Dmitry Osipenko

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=5e5d4592-7ff4-2de2-eff1-ad5e006861b0@gmail.com \
    --to=digetx@gmail.com \
    --cc=Markus.Elfring@web.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.com \
    --cc=wsa@the-dreams.de \
    /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).