Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jun Yan <jerrysteve1101@gmail.com>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] iio: gyro: bmg160_i2c: add BMI088 to of_match_table
Date: Sat, 22 Feb 2025 16:40:13 +0000	[thread overview]
Message-ID: <20250222164013.0a5aae07@jic23-huawei> (raw)
In-Reply-To: <20250220165001.273325-3-jerrysteve1101@gmail.com>

On Fri, 21 Feb 2025 00:50:01 +0800
Jun Yan <jerrysteve1101@gmail.com> wrote:

> BMI088 is missing from the of_match_table. Let's complete it.
> 
> Signed-off-by: Jun Yan <jerrysteve1101@gmail.com>
Applied this patch. I'll initially push out as testing for 0-day to
see if it can find any problems.

Thanks,

Jonathan
> ---
>  drivers/iio/gyro/bmg160_i2c.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/iio/gyro/bmg160_i2c.c b/drivers/iio/gyro/bmg160_i2c.c
> index 9c5d7e8ee99c..e6caab49f98a 100644
> --- a/drivers/iio/gyro/bmg160_i2c.c
> +++ b/drivers/iio/gyro/bmg160_i2c.c
> @@ -58,6 +58,7 @@ MODULE_DEVICE_TABLE(i2c, bmg160_i2c_id);
>  static const struct of_device_id bmg160_of_match[] = {
>  	{ .compatible = "bosch,bmg160" },
>  	{ .compatible = "bosch,bmi055_gyro" },
> +	{ .compatible = "bosch,bmi088_gyro" },
>  	{ }
>  };
>  


      reply	other threads:[~2025-02-22 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 16:49 [PATCH v2 0/2] iio: gyro: bmg160: Improve BMG160 driver with of_match_table support Jun Yan
2025-02-20 16:50 ` [PATCH v2 1/2] iio: gyro: bmg160_spi: add of_match_table Jun Yan
2025-02-22 16:37   ` Jonathan Cameron
2025-03-06 14:18     ` yjun
2025-02-20 16:50 ` [PATCH v2 2/2] iio: gyro: bmg160_i2c: add BMI088 to of_match_table Jun Yan
2025-02-22 16:40   ` Jonathan Cameron [this message]

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=20250222164013.0a5aae07@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=jerrysteve1101@gmail.com \
    --cc=lars@metafoo.de \
    --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