linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jie Deng <jie.deng@intel.com>,
	linux-i2c@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, mst@redhat.com, arnd@arndb.de,
	jasowang@redhat.com, yu1.wang@intel.com, shuo.a.liu@intel.com,
	conghui.chen@intel.com, viresh.kumar@linaro.org,
	stefanha@redhat.com
Subject: Re: [PATCH v12] i2c: virtio: add a virtio i2c frontend driver
Date: Sat, 3 Jul 2021 01:01:34 +0200	[thread overview]
Message-ID: <YN+azpQsgAK9MbYd@kunai> (raw)
In-Reply-To: <YN7jOm68fUL4UA2Q@smile.fi.intel.com>

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]


> It's _BITUL() or so from linux/const.h.
> https://elixir.bootlin.com/linux/latest/source/include/uapi/linux/const.h#L28
> You may not use internal definitions in UAPI headers.

Sorry, I missed it was an uapi header and gave the authors bad advice
with BIT.

If I get another fixed version by Saturday evening (CEST), I can still
squeeze it into my pull request for 5.14. Minor details can be fixed
incrementally, but we definatel need to get the uapi header correct.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-07-02 23:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  8:46 [PATCH v12] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2021-07-02  9:58 ` Andy Shevchenko
2021-07-02 23:01   ` Wolfram Sang [this message]
2021-07-05  2:43   ` Viresh Kumar
2021-07-05  3:01     ` Jie Deng
2021-07-05  6:21     ` Jie Deng
2021-07-05  6:31       ` Viresh Kumar
2021-07-05  3:46   ` Jie Deng
2021-07-05  2:40 ` Viresh Kumar
2021-07-05  3:45   ` Jie Deng
2021-07-05  4:38     ` Viresh Kumar
2021-07-05  6:22       ` Jie Deng
2021-07-05  6:30         ` Viresh Kumar
2021-07-05  7:13           ` Jie Deng

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=YN+azpQsgAK9MbYd@kunai \
    --to=wsa@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=conghui.chen@intel.com \
    --cc=jasowang@redhat.com \
    --cc=jie.deng@intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=shuo.a.liu@intel.com \
    --cc=stefanha@redhat.com \
    --cc=viresh.kumar@linaro.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=yu1.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;
as well as URLs for NNTP newsgroup(s).