All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Werner <wernerandy-Mmb7MZpHnFY@public.gmane.org>
To: Joe Perches <joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
Cc: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>,
	wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
	jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org,
	baohua.song-kQvG35nSl+M@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] I2C: busses: Do not print error message in syslog if no ACK received
Date: Thu, 14 Nov 2013 19:26:09 +0100	[thread overview]
Message-ID: <20131114182609.GB2133@thinkpad.fritz.box> (raw)
In-Reply-To: <1384436392.15774.2.camel@joe-AO722>

On Thu, Nov 14, 2013 at 05:39:52AM -0800, Joe Perches wrote:
> On Wed, 2013-11-13 at 20:24 +0100, Marek Vasut wrote:
> > > On Tue, Nov 12, 2013 at 07:33:40PM +0100, Marek Vasut wrote:
> > > > > > That is because if you look at the only caller of this function,
> > > > > > which is pch_i2c_wait_for_check_xfer(), you will see that at the
> > > > > > only place where pch_i2c_getack() is called there is already
> > > > > > pch_dbg():
> > > > > > 
> > > > > > 369         if (pch_i2c_getack(adap)) {
> > > > > > 370                 pch_dbg(adap, "Receive NACK for slave address"
> > > > > > 371                         "setting\n");
> > > > > > 372                 return -EIO;
> > > > > > 373         }
> > > 
> > > Sorry i misunderstood that. You are absolutly right, thats the best
> > > solution for that. Remove the pch_err at getack so that only the pch_dbg
> > > get printed where getack is called. This should be enough information.
> > 
> > No problem ;-)
> 
> If this is the approach taken, please coalesce the format.
> As is there's a missing space between address and setting.
> This should be:
> 
> 		pch_dbg(adap, "Received NACK for slave address setting\n");
> 
> 
Hi,
yes you are right, i will also add it and resand the patch in a few days.

regards 
Andy

WARNING: multiple messages have this Message-ID (diff)
From: Andreas Werner <wernerandy@gmx.de>
To: Joe Perches <joe@perches.com>
Cc: Marek Vasut <marex@denx.de>,
	wsa@the-dreams.de, jacmet@sunsite.dk, baohua.song@csr.com,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] I2C: busses: Do not print error message in syslog if no ACK received
Date: Thu, 14 Nov 2013 19:26:09 +0100	[thread overview]
Message-ID: <20131114182609.GB2133@thinkpad.fritz.box> (raw)
In-Reply-To: <1384436392.15774.2.camel@joe-AO722>

On Thu, Nov 14, 2013 at 05:39:52AM -0800, Joe Perches wrote:
> On Wed, 2013-11-13 at 20:24 +0100, Marek Vasut wrote:
> > > On Tue, Nov 12, 2013 at 07:33:40PM +0100, Marek Vasut wrote:
> > > > > > That is because if you look at the only caller of this function,
> > > > > > which is pch_i2c_wait_for_check_xfer(), you will see that at the
> > > > > > only place where pch_i2c_getack() is called there is already
> > > > > > pch_dbg():
> > > > > > 
> > > > > > 369         if (pch_i2c_getack(adap)) {
> > > > > > 370                 pch_dbg(adap, "Receive NACK for slave address"
> > > > > > 371                         "setting\n");
> > > > > > 372                 return -EIO;
> > > > > > 373         }
> > > 
> > > Sorry i misunderstood that. You are absolutly right, thats the best
> > > solution for that. Remove the pch_err at getack so that only the pch_dbg
> > > get printed where getack is called. This should be enough information.
> > 
> > No problem ;-)
> 
> If this is the approach taken, please coalesce the format.
> As is there's a missing space between address and setting.
> This should be:
> 
> 		pch_dbg(adap, "Received NACK for slave address setting\n");
> 
> 
Hi,
yes you are right, i will also add it and resand the patch in a few days.

regards 
Andy

  reply	other threads:[~2013-11-14 18:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 17:45 [PATCH] I2C: busses: Do not print error message in syslog if no ACK received Andreas Werner
2013-11-12 18:00 ` Marek Vasut
     [not found]   ` <201311121900.59305.marex-ynQEQJNshbs@public.gmane.org>
2013-11-12 18:23     ` Andreas Werner
2013-11-12 18:23       ` Andreas Werner
     [not found]       ` <20131112182344.GA5012-Zv899e0YUSYXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2013-11-12 18:33         ` Marek Vasut
2013-11-12 18:33           ` Marek Vasut
     [not found]           ` <201311121933.41038.marex-ynQEQJNshbs@public.gmane.org>
2013-11-13 18:24             ` Andreas Werner
2013-11-13 18:24               ` Andreas Werner
     [not found]               ` <20131113182415.GA1458-Zv899e0YUSYXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2013-11-13 19:24                 ` Marek Vasut
2013-11-13 19:24                   ` Marek Vasut
     [not found]                   ` <201311132024.06853.marex-ynQEQJNshbs@public.gmane.org>
2013-11-14 13:39                     ` Joe Perches
2013-11-14 13:39                       ` Joe Perches
2013-11-14 18:26                       ` Andreas Werner [this message]
2013-11-14 18:26                         ` Andreas Werner

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=20131114182609.GB2133@thinkpad.fritz.box \
    --to=wernerandy-mmb7mzphnfy@public.gmane.org \
    --cc=baohua.song-kQvG35nSl+M@public.gmane.org \
    --cc=jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org \
    --cc=joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marex-ynQEQJNshbs@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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.