From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: kernel test robot <lkp@intel.com>
Cc: linux1394-devel@lists.sourceforge.net, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 17/17] firewire: ohci: use guard macro to serialize operations for isochronous contexts
Date: Mon, 5 Aug 2024 17:33:45 +0900 [thread overview]
Message-ID: <20240805083345.GA248096@workstation.local> (raw)
In-Reply-To: <202408050730.y1eyRcTv-lkp@intel.com>
On Mon, Aug 05, 2024 at 07:33:01AM +0800, kernel test robot wrote:
> url: https://github.com/intel-lab-lkp/linux/commits/Takashi-Sakamoto/firewire-core-use-guard-macro-to-maintain-static-packet-data-for-phy-configuration/20240804-210645
> base: https://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git for-next
> patch link: https://lore.kernel.org/r/20240804130225.243496-18-o-takashi%40sakamocchi.jp
> patch subject: [PATCH 17/17] firewire: ohci: use guard macro to serialize operations for isochronous contexts
> config: arm64-randconfig-003-20240805 (https://download.01.org/0day-ci/archive/20240805/202408050730.y1eyRcTv-lkp@intel.com/config)
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240805/202408050730.y1eyRcTv-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202408050730.y1eyRcTv-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> drivers/firewire/ohci.c:3138:2: error: expected expression
> 3138 | guard(spinlock_irq)(&ohci->lock);
> | ^
> include/linux/cleanup.h:167:2: note: expanded from macro 'guard'
> 167 | CLASS(_name, __UNIQUE_ID(guard))
> | ^
> include/linux/cleanup.h:122:2: note: expanded from macro 'CLASS'
> 122 | class_##_name##_t var __cleanup(class_##_name##_destructor) = \
> | ^
> <scratch space>:133:1: note: expanded from here
> 133 | class_spinlock_irq_t
> | ^
> 1 error generated.
The macro expands a declaration, while the line just after the label
should be still any statement in C11.
I'll post take 2 patchset.
Thanks
Takashi Sakamoto
prev parent reply other threads:[~2024-08-05 8:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 13:02 [PATCH 00/17] firewire: core/ohci: use guard macro for any type of lock primitives Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 01/17] firewire: core: use guard macro to maintain static packet data for phy configuration Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 02/17] firewire: core: use guard macro to maintain the list of card Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 03/17] firewire: core: use guard macro to maintain the list of cdev clients Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 04/17] firewire: ohci: use guard macro to serialize accesses to phy registers Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 05/17] firewire: core: use guard macro to maintain RCU scope for transaction address handler Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 06/17] firewire: core: use guard macro to access to IDR for fw_device Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 07/17] firewire: core: use guard macro to maintain the list of address handler for transaction Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 08/17] firewire: core: use guard macro to disable local IRQ Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 09/17] firewire: core: use guard macro to maintain list of events for userspace clients Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 10/17] firewire: core: use guard macro to maintain IDR of isochronous resources " Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 11/17] firewire: core: use guard macro to maintain isochronous context for userspace client Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 12/17] firewire: core: use guard macro to maintain list of receivers for phy configuration packets Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 13/17] firewire: core: use guard macro to maintain list of asynchronous transaction Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 14/17] firewire: core: use guard macro to maintain properties of fw_card Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 15/17] firewire: ohci: use guard macro to maintain bus time Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 16/17] firewire: ohci: use guard macro to maintain image of configuration ROM Takashi Sakamoto
2024-08-04 13:02 ` [PATCH 17/17] firewire: ohci: use guard macro to serialize operations for isochronous contexts Takashi Sakamoto
2024-08-04 22:31 ` kernel test robot
2024-08-04 23:33 ` kernel test robot
2024-08-05 8:33 ` Takashi Sakamoto [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=20240805083345.GA248096@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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