From: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>
To: Jean-Baptiste Maneyrol <JManeyrol@invensense.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: imu: inv_mpu6050: add header include protection macro
Date: Mon, 5 Aug 2019 17:32:26 +0100 [thread overview]
Message-ID: <20190805173226.71757a05@archlinux> (raw)
In-Reply-To: <20190805122513.8399-1-jmaneyrol@invensense.com>
On Mon, 5 Aug 2019 12:25:43 +0000
Jean-Baptiste Maneyrol <JManeyrol@invensense.com> wrote:
> Signed-off-by: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
No problem with adding this, but why specifically did you do so?
Thanks,
Jonathan
> ---
> drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h b/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h
> index db1c6904388b..e64eb978e810 100644
> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h
> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h
> @@ -2,6 +2,10 @@
> /*
> * Copyright (C) 2012 Invensense, Inc.
> */
> +
> +#ifndef INV_MPU_IIO_H_
> +#define INV_MPU_IIO_H_
> +
> #include <linux/i2c.h>
> #include <linux/i2c-mux.h>
> #include <linux/mutex.h>
> @@ -342,3 +346,5 @@ void inv_mpu_acpi_delete_mux_client(struct i2c_client *client);
> int inv_mpu_core_probe(struct regmap *regmap, int irq, const char *name,
> int (*inv_mpu_bus_setup)(struct iio_dev *), int chip_type);
> extern const struct dev_pm_ops inv_mpu_pmops;
> +
> +#endif
next prev parent reply other threads:[~2019-08-05 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 12:25 [PATCH] iio: imu: inv_mpu6050: add header include protection macro Jean-Baptiste Maneyrol
2019-08-05 16:32 ` Jonathan Cameron [this message]
2019-08-06 8:05 ` Jean-Baptiste Maneyrol
2019-08-06 9:15 ` Jonathan Cameron
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=20190805173226.71757a05@archlinux \
--to=jic23@jic23.retrosnub.co.uk \
--cc=JManeyrol@invensense.com \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).