From: Andrea Merello <andrea.merello@gmail.com> To: Andy Shevchenko <andy.shevchenko@gmail.com> Cc: kernel test robot <lkp@intel.com>, Jonathan Cameron <jic23@kernel.org>, Mauro Carvalho Chehab <mchehab+huawei@kernel.org>, linux-iio <linux-iio@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, devicetree <devicetree@vger.kernel.org>, kbuild-all@lists.01.org, Lars-Peter Clausen <lars@metafoo.de>, Rob Herring <robh+dt@kernel.org>, Matt Ranostay <matt.ranostay@konsulko.com>, Alexandru Ardelean <ardeleanalex@gmail.com>, jmondi <jacopo@jmondi.org>, Andrea Merello <andrea.merello@iit.it> Subject: Re: [v5 12/14] iio: imu: add BNO055 serdev driver Date: Tue, 3 May 2022 15:30:08 +0200 [thread overview] Message-ID: <CAN8YU5PNUn9oVz9dRZ7BLzZmqfNpTehJp284ou+Y7-e4XgK7_Q@mail.gmail.com> (raw) In-Reply-To: <CAN8YU5OeYjf5pikMuLXyaYTO1bsArdFOQf3M6tYMNubeZxqe7A@mail.gmail.com> Il giorno mar 3 mag 2022 alle ore 09:48 Andrea Merello <andrea.merello@gmail.com> ha scritto: [...] > > You need to add a C-file with the only line > > > > #include <..._trace.h> > > > > And drop that include from the _core.c. > > Hum, I'm a bit confused here: the bno055_ser_core.c file explicitly > looks for that tracepoints (e.g. it calls trace_send_chunks() and > friends); dropping the include prevents build here because there would > be no definition for those tracepoints. > > There is already a C file bno055_ser_trace.c that just contains the > said include and it defines CREATE_TRACE_POINTS; I see other drivers > like dwc3 do the same.. Oops.. it turned out that I just had this almost-empty C file as untracked in my git tree, and it ended up not being included in patches also. Being it laying in my src tree caused the build to succeed. I have been misled by the other problem I (still) have (below); I was focused on the wrong thing, sorry. > But my problem is that I cannot reproduce the issue found by the bot: > the compiler that is downloaded by the script doesn't run on my build > box because it wants a newer libc (I was hoping that those compilers > were statically linked, but they aren't), while any other attempt I > did with other older compilers resulted in either successful build or > failed with other weird, apparently unrelated, errors about relocation > issues (of course I tried with the arch and config used by the build > bot). > > Is there any build farm publicly available or something like that? > > > -- > > With Best Regards, > > Andy Shevchenko
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Merello <andrea.merello@gmail.com> To: kbuild-all@lists.01.org Subject: Re: [v5 12/14] iio: imu: add BNO055 serdev driver Date: Tue, 03 May 2022 15:30:08 +0200 [thread overview] Message-ID: <CAN8YU5PNUn9oVz9dRZ7BLzZmqfNpTehJp284ou+Y7-e4XgK7_Q@mail.gmail.com> (raw) In-Reply-To: <CAN8YU5OeYjf5pikMuLXyaYTO1bsArdFOQf3M6tYMNubeZxqe7A@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1636 bytes --] Il giorno mar 3 mag 2022 alle ore 09:48 Andrea Merello <andrea.merello@gmail.com> ha scritto: [...] > > You need to add a C-file with the only line > > > > #include <..._trace.h> > > > > And drop that include from the _core.c. > > Hum, I'm a bit confused here: the bno055_ser_core.c file explicitly > looks for that tracepoints (e.g. it calls trace_send_chunks() and > friends); dropping the include prevents build here because there would > be no definition for those tracepoints. > > There is already a C file bno055_ser_trace.c that just contains the > said include and it defines CREATE_TRACE_POINTS; I see other drivers > like dwc3 do the same.. Oops.. it turned out that I just had this almost-empty C file as untracked in my git tree, and it ended up not being included in patches also. Being it laying in my src tree caused the build to succeed. I have been misled by the other problem I (still) have (below); I was focused on the wrong thing, sorry. > But my problem is that I cannot reproduce the issue found by the bot: > the compiler that is downloaded by the script doesn't run on my build > box because it wants a newer libc (I was hoping that those compilers > were statically linked, but they aren't), while any other attempt I > did with other older compilers resulted in either successful build or > failed with other weird, apparently unrelated, errors about relocation > issues (of course I tried with the arch and config used by the build > bot). > > Is there any build farm publicly available or something like that? > > > -- > > With Best Regards, > > Andy Shevchenko
next prev parent reply other threads:[~2022-05-03 13:30 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 13:10 [v5 00/14] Add support for Bosch BNO055 IMU Andrea Merello 2022-04-26 13:10 ` [v5 01/14] iio: add modifiers for linear acceleration Andrea Merello 2022-04-26 13:10 ` [v5 02/14] iio: document linear acceleration modifiers Andrea Merello 2022-04-26 13:10 ` [v5 03/14] iio: event_monitor: add " Andrea Merello 2022-04-26 13:10 ` [v5 04/14] iio: add modifers for pitch, yaw, roll Andrea Merello 2022-04-26 13:10 ` [v5 05/14] iio: document pitch, yaw, roll modifiers Andrea Merello 2022-04-26 13:10 ` [v5 06/14] iio: event_monitor: add pitch, yaw and " Andrea Merello 2022-04-26 13:10 ` [v5 07/14] iio: add support for binary attributes Andrea Merello 2022-04-26 13:10 ` [v5 08/14] iio: imu: add Bosch Sensortec BNO055 core driver Andrea Merello 2022-04-27 13:22 ` Andy Shevchenko 2022-05-02 9:50 ` Andrea Merello 2022-05-02 10:11 ` Andy Shevchenko 2022-05-02 13:12 ` Andrea Merello 2022-04-26 13:10 ` [v5 09/14] iio: document bno055 private sysfs attributes Andrea Merello 2022-04-26 13:10 ` [v5 10/14] iio: document "serialnumber" sysfs attribute Andrea Merello 2022-04-26 13:10 ` [v5 11/14] dt-bindings: iio/imu: Add Bosch BNO055 Andrea Merello 2022-04-26 13:11 ` [v5 12/14] iio: imu: add BNO055 serdev driver Andrea Merello 2022-04-27 8:10 ` kernel test robot 2022-04-27 13:41 ` Andy Shevchenko 2022-04-27 13:41 ` Andy Shevchenko 2022-05-03 7:48 ` Andrea Merello 2022-05-03 7:48 ` Andrea Merello 2022-05-03 13:30 ` Andrea Merello [this message] 2022-05-03 13:30 ` Andrea Merello 2022-05-03 14:04 ` Andy Shevchenko 2022-05-03 14:04 ` Andy Shevchenko 2022-04-27 14:24 ` kernel test robot 2022-04-26 13:11 ` [v5 13/14] iio: imu: add BNO055 I2C driver Andrea Merello 2022-04-26 13:11 ` [v5 14/14] docs: iio: add documentation for BNO055 driver Andrea Merello 2022-04-27 13:42 ` [v5 00/14] Add support for Bosch BNO055 IMU Andy Shevchenko 2022-05-01 17:03 ` Jonathan Cameron 2022-05-02 6:33 ` Andrea Merello 2022-05-02 7:47 ` Andy Shevchenko 2022-05-02 8:31 ` Andrea Merello 2022-05-02 8:52 ` Andy Shevchenko
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=CAN8YU5PNUn9oVz9dRZ7BLzZmqfNpTehJp284ou+Y7-e4XgK7_Q@mail.gmail.com \ --to=andrea.merello@gmail.com \ --cc=andrea.merello@iit.it \ --cc=andy.shevchenko@gmail.com \ --cc=ardeleanalex@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=jacopo@jmondi.org \ --cc=jic23@kernel.org \ --cc=kbuild-all@lists.01.org \ --cc=lars@metafoo.de \ --cc=linux-iio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@intel.com \ --cc=matt.ranostay@konsulko.com \ --cc=mchehab+huawei@kernel.org \ --cc=robh+dt@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.