From: Tony Lindgren <tony@atomide.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Jonathan Cameron <jic23@kernel.org>,
kbuild-all@01.org, Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-omap@vger.kernel.org,
Marcel Partap <mpartap@gmx.net>,
Michael Scott <michael.scott@linaro.org>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH 1/3] iio: adc: cpcap: Fix default register values and battery temperature (fwd)
Date: Wed, 24 May 2017 08:46:12 -0700 [thread overview]
Message-ID: <20170524154612.GZ10472@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705240938520.2983@hadrien>
Hi,
* Julia Lawall <julia.lawall@lip6.fr> [170524 00:43]:
> CPCAP_BIT_ADTRIG_DIS is duplicated on lines 77-82.
> 02e16000 Tony Lindgren 2017-05-22 77 #define CPCAP_REG_ADCC2_DEFAULTS (CPCAP_BIT_AD4_SELECT | \
> 02e16000 Tony Lindgren 2017-05-22 @78 CPCAP_BIT_ADTRIG_DIS | \
> 02e16000 Tony Lindgren 2017-05-22 79 CPCAP_BIT_ADTRIG_DIS | \
Oops, thanks for letting me know.
Jonathan, do you want an incremental patch or v3 of the whole set resent?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Julia Lawall <julia.lawall-L2FTfq7BK8M@public.gmane.org>
Cc: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
kbuild-all-JC7UmRfGjtg@public.gmane.org,
Hartmut Knaack <knaack.h-Mmb7MZpHnFY@public.gmane.org>,
Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>,
Peter Meerwald-Stadler
<pmeerw-jW+XmwGofnusTnJN9+BGXg@public.gmane.org>,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Marcel Partap <mpartap-hi6Y0CQ0nG0@public.gmane.org>,
Michael Scott
<michael.scott-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 1/3] iio: adc: cpcap: Fix default register values and battery temperature (fwd)
Date: Wed, 24 May 2017 08:46:12 -0700 [thread overview]
Message-ID: <20170524154612.GZ10472@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705240938520.2983@hadrien>
Hi,
* Julia Lawall <julia.lawall-L2FTfq7BK8M@public.gmane.org> [170524 00:43]:
> CPCAP_BIT_ADTRIG_DIS is duplicated on lines 77-82.
> 02e16000 Tony Lindgren 2017-05-22 77 #define CPCAP_REG_ADCC2_DEFAULTS (CPCAP_BIT_AD4_SELECT | \
> 02e16000 Tony Lindgren 2017-05-22 @78 CPCAP_BIT_ADTRIG_DIS | \
> 02e16000 Tony Lindgren 2017-05-22 79 CPCAP_BIT_ADTRIG_DIS | \
Oops, thanks for letting me know.
Jonathan, do you want an incremental patch or v3 of the whole set resent?
Regards,
Tony
next prev parent reply other threads:[~2017-05-24 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 7:39 [PATCH 1/3] iio: adc: cpcap: Fix default register values and battery temperature (fwd) Julia Lawall
2017-05-24 7:39 ` Julia Lawall
2017-05-24 15:46 ` Tony Lindgren [this message]
2017-05-24 15:46 ` Tony Lindgren
2017-05-24 19:41 ` Jonathan Cameron
2017-05-24 19:41 ` Jonathan Cameron
2017-05-24 22:01 ` Tony Lindgren
2017-05-24 22:01 ` Tony Lindgren
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=20170524154612.GZ10472@atomide.com \
--to=tony@atomide.com \
--cc=jic23@kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=michael.scott@linaro.org \
--cc=mpartap@gmx.net \
--cc=pmeerw@pmeerw.net \
--cc=sre@kernel.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.