From: Paul Lemmermann <thepaulodoom@thepaulodoom.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IIO: accel: dmard09: fixed code styling issues
Date: Sat, 2 Apr 2022 15:02:09 -0500 [thread overview]
Message-ID: <YkirwZaMWfgNTtS1@hp-amd-paul> (raw)
In-Reply-To: <20220402172814.5117cdb7@jic23-huawei>
On Sat, Apr 02, 2022 at 05:28:14PM +0100, Jonathan Cameron wrote:
> On Mon, 28 Mar 2022 16:48:16 -0500
> Paul Lemmermann <thepaulodoom@thepaulodoom.com> wrote:
>
> > Cleaning up code.
> >
> > Signed-off-by: Paul Lemmermann <thepaulodoom@thepaulodoom.com>
> Applied to the togreg branch of iio.git and pushed out as testing
> for 0-day to see if it can find anything we did wrong.
>
> BTW. You seem to have sent two identical copies of this patch.
> I randomly decided to apply this second one.
Yes, I accidentally sent two identical patches. Sorry!
Thank you so much for applying my patch,
Paul
>
> Thanks,
>
> Jonathan
>
> > ---
> > drivers/iio/accel/dmard09.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/accel/dmard09.c b/drivers/iio/accel/dmard09.c
> > index 53ab6078c..cb0246ca7 100644
> > --- a/drivers/iio/accel/dmard09.c
> > +++ b/drivers/iio/accel/dmard09.c
> > @@ -24,7 +24,7 @@
> > #define DMARD09_AXIS_Y 1
> > #define DMARD09_AXIS_Z 2
> > #define DMARD09_AXIS_X_OFFSET ((DMARD09_AXIS_X + 1) * 2)
> > -#define DMARD09_AXIS_Y_OFFSET ((DMARD09_AXIS_Y + 1 )* 2)
> > +#define DMARD09_AXIS_Y_OFFSET ((DMARD09_AXIS_Y + 1) * 2)
> > #define DMARD09_AXIS_Z_OFFSET ((DMARD09_AXIS_Z + 1) * 2)
> >
> > struct dmard09_data {
>
next prev parent reply other threads:[~2022-04-02 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 21:48 [PATCH] IIO: accel: dmard09: fixed code styling issues Paul Lemmermann
2022-04-02 16:28 ` Jonathan Cameron
2022-04-02 20:02 ` Paul Lemmermann [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-28 21:28 Paul Lemmermann
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=YkirwZaMWfgNTtS1@hp-amd-paul \
--to=thepaulodoom@thepaulodoom.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox