linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Jie Deng <jie.deng@intel.com>, kernel test robot <lkp@intel.com>,
	linux-i2c@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, wsa@kernel.org,
	wsa+renesas@sang-engineering.com, mst@redhat.com, arnd@arndb.de,
	jasowang@redhat.com, andriy.shevchenko@linux.intel.com
Subject: Re: [kbuild-all] Re: [PATCH v11] i2c: virtio: add a virtio i2c frontend driver
Date: Fri, 2 Jul 2021 14:38:52 +0800	[thread overview]
Message-ID: <8e5e81b0-37f5-3863-9a9e-c66bf2a9d42f@intel.com> (raw)
In-Reply-To: <68b2b36b-f1ee-d1aa-d4a5-d45f36602be6@intel.com>



On 7/2/21 11:12 AM, Jie Deng wrote:
>
> On 2021/7/1 18:00, kernel test robot wrote:
>> Hi Jie,
>>
>> Thank you for the patch! Yet something to improve:
>>
>> [auto build test ERROR on wsa/i2c/for-next]
>> [also build test ERROR on linux/master linus/master v5.13 next-20210630]
>> [cannot apply to vhost/linux-next]
>> [If your patch is applied to the wrong git tree, kindly drop us a note.
>> And when submitting patch, we suggest to use '--base' as documented in
>> https://git-scm.com/docs/git-format-patch]
>>
>> url: 
>> https://github.com/0day-ci/linux/commits/Jie-Deng/i2c-virtio-add-a-virtio-i2c-frontend-driver/20210701-112619
>> base: https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git 
>> i2c/for-next
>> config: i386-randconfig-c021-20210630 (attached as .config)
>> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
>> reproduce (this is a W=1 build):
>>          # 
>> https://github.com/0day-ci/linux/commit/e8dedd2a8577148d7655d0affe35adf34efbbf15
>>          git remote add linux-review https://github.com/0day-ci/linux
>>          git fetch --no-tags linux-review 
>> Jie-Deng/i2c-virtio-add-a-virtio-i2c-frontend-driver/20210701-112619
>>          git checkout e8dedd2a8577148d7655d0affe35adf34efbbf15
>>          # save the attached .config to linux build tree
>>          mkdir build_dir
>>          make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>>     In file included from <command-line>:32:
>>>> ./usr/include/linux/virtio_i2c.h:12:10: fatal error: linux/bits.h: 
>>>> No such file or directory
>>        12 | #include <linux/bits.h>
>>           |          ^~~~~~~~~~~~~~
>>     compilation terminated.
>
>
> I didn't see this error. Why did you say no such file? Anything wrong ?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git/tree/include/linux/bits.h 
>
>
> Thank you !


Hi Jie,

The problem is reproducible, I guess it's due to bits.h not in 
include/uapi/linux.

Best Regards,
Rong Chen

  reply	other threads:[~2021-07-02  6:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  3:24 [PATCH v11] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2021-07-01  4:04 ` Viresh Kumar
2021-07-01  6:10   ` Jie Deng
2021-07-01  6:18     ` Viresh Kumar
2021-07-02  3:36       ` Jie Deng
2021-07-02  4:56         ` Viresh Kumar
2021-07-01 19:24   ` Wolfram Sang
2021-07-02  4:55     ` Viresh Kumar
2021-07-02  6:22       ` Wolfram Sang
2021-07-02  6:52       ` Jie Deng
2021-07-02  6:56         ` Viresh Kumar
2021-07-02  7:11           ` Wolfram Sang
2021-07-02  7:15           ` Jie Deng
2021-07-02  7:21             ` Viresh Kumar
2021-07-02  7:36               ` Wolfram Sang
2021-07-01  8:50 ` kernel test robot
2021-07-01 10:00 ` kernel test robot
2021-07-02  3:12   ` Jie Deng
2021-07-02  6:38     ` Rong Chen [this message]
2021-07-01 10:45 ` Andy Shevchenko
2021-07-02  1:05   ` 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=8e5e81b0-37f5-3863-9a9e-c66bf2a9d42f@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=jasowang@redhat.com \
    --cc=jie.deng@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@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).