public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Wentong Wu <wentong.wu@intel.com>,
	gregkh@linuxfoundation.org, arnd@arndb.de, mka@chromium.org,
	oneukum@suse.com, lee@kernel.org, wsa@kernel.org,
	kfting@nuvoton.com, broonie@kernel.org, linus.walleij@linaro.org,
	hdegoede@redhat.com, maz@kernel.org, brgl@bgdev.pl,
	linux-usb@vger.kernel.org, linux-i2c@vger.kernel.org,
	linux-spi@vger.kernel.org, linux-gpio@vger.kernel.org,
	andriy.shevchenko@linux.intel.com,
	heikki.krogerus@linux.intel.com, andi.shyti@linux.intel.com,
	sakari.ailus@linux.intel.com, bartosz.golaszewski@linaro.org,
	srinivas.pandruvada@intel.com
Cc: zhifeng.wang@intel.com
Subject: Re: [PATCH v16 1/4] usb: Add support for Intel LJCA device
Date: Wed, 13 Sep 2023 11:03:33 +0200	[thread overview]
Message-ID: <a3b75e11-9cf0-4ee3-be90-fba73bd5df3d@suse.com> (raw)
In-Reply-To: <1694569212-10080-2-git-send-email-wentong.wu@intel.com>



On 13.09.23 03:40, Wentong Wu wrote:

> +struct ljca_bank_descriptor {
> +	u8 bank_id;
> +	u8 pin_num;
> +
> +	/* 1 bit for each gpio, 1 means valid */
> +	u32 valid_pins;

No endianness?

> +} __packed;

	Regards
		Oliver

  parent reply	other threads:[~2023-09-13  9:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13  1:40 [PATCH v16 0/4] Add Intel LJCA device driver Wentong Wu
2023-09-13  1:40 ` [PATCH v16 1/4] usb: Add support for Intel LJCA device Wentong Wu
2023-09-13  6:12   ` kernel test robot
2023-09-13  7:26     ` Hans de Goede
2023-09-13  8:10       ` Wu, Wentong
2023-09-13  9:03   ` Oliver Neukum [this message]
2023-09-14  1:05     ` Wu, Wentong
2023-09-14  8:21       ` Hans de Goede
2023-09-14  8:58         ` Wu, Wentong
2023-09-13  1:40 ` [PATCH v16 2/4] i2c: Add support for Intel LJCA USB I2C driver Wentong Wu
2023-09-13  1:40 ` [PATCH v16 3/4] spi: Add support for Intel LJCA USB SPI driver Wentong Wu
2023-09-13  1:40 ` [PATCH v16 4/4] gpio: update Intel LJCA USB GPIO driver Wentong Wu

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=a3b75e11-9cf0-4ee3-be90-fba73bd5df3d@suse.com \
    --to=oneukum@suse.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kfting@nuvoton.com \
    --cc=lee@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=mka@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=srinivas.pandruvada@intel.com \
    --cc=wentong.wu@intel.com \
    --cc=wsa@kernel.org \
    --cc=zhifeng.wang@intel.com \
    /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