From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com> To: kernel test robot <lkp@intel.com> Cc: kbuild-all@lists.01.org, Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>, Bjorn Andersson <bjorn.andersson@linaro.org>, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-power@fi.rohmeurope.com, linux-arm-msm@vger.kernel.org Subject: Re: [PATCH v4 3/7] regulator: IRQ based event/error notification helpers Date: Tue, 06 Apr 2021 13:57:19 +0300 [thread overview] Message-ID: <7706d59fe7120106e4695fd83da5b089d5a36d87.camel@fi.rohmeurope.com> (raw) In-Reply-To: <202104061806.LUDNu0F6-lkp@intel.com> On Tue, 2021-04-06 at 18:27 +0800, kernel test robot wrote: > 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 include/linux/kernel.h:16, > from arch/x86/include/asm/percpu.h:27, > from arch/x86/include/asm/current.h:6, > from include/linux/sched.h:12, > from include/linux/ratelimit.h:6, > from include/linux/dev_printk.h:16, > from include/linux/device.h:15, > from drivers/regulator/irq_helpers.c:10: > drivers/regulator/irq_helpers.c: In function 'die_loudly': > > > drivers/regulator/irq_helpers.c:46:11: error: expected ')' before > > > 'msg' > 46 | pr_emerg(msg); > | ^~~ > include/linux/printk.h:301:21: note: in definition of macro > 'pr_fmt' > 301 | #define pr_fmt(fmt) fmt > | ^~~ > drivers/regulator/irq_helpers.c:46:2: note: in expansion of macro > 'pr_emerg' > 46 | pr_emerg(msg); > | ^~~~~~~~ Ouch. Feeling stupid now. I am sorry for the hassle folks. I'll fix this ASAP and resend. > > vim +46 drivers/regulator/irq_helpers.c > > 43 > 44 static void die_loudly(const char *msg) > 45 { > > 46 pr_emerg(msg); > 47 BUG(); > 48 } > 49 Best Regards Matti Vaittinen
WARNING: multiple messages have this Message-ID (diff)
From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH v4 3/7] regulator: IRQ based event/error notification helpers Date: Tue, 06 Apr 2021 13:57:19 +0300 [thread overview] Message-ID: <7706d59fe7120106e4695fd83da5b089d5a36d87.camel@fi.rohmeurope.com> (raw) In-Reply-To: <202104061806.LUDNu0F6-lkp@intel.com> [-- Attachment #1: Type: text/plain, Size: 1521 bytes --] On Tue, 2021-04-06 at 18:27 +0800, kernel test robot wrote: > 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 include/linux/kernel.h:16, > from arch/x86/include/asm/percpu.h:27, > from arch/x86/include/asm/current.h:6, > from include/linux/sched.h:12, > from include/linux/ratelimit.h:6, > from include/linux/dev_printk.h:16, > from include/linux/device.h:15, > from drivers/regulator/irq_helpers.c:10: > drivers/regulator/irq_helpers.c: In function 'die_loudly': > > > drivers/regulator/irq_helpers.c:46:11: error: expected ')' before > > > 'msg' > 46 | pr_emerg(msg); > | ^~~ > include/linux/printk.h:301:21: note: in definition of macro > 'pr_fmt' > 301 | #define pr_fmt(fmt) fmt > | ^~~ > drivers/regulator/irq_helpers.c:46:2: note: in expansion of macro > 'pr_emerg' > 46 | pr_emerg(msg); > | ^~~~~~~~ Ouch. Feeling stupid now. I am sorry for the hassle folks. I'll fix this ASAP and resend. > > vim +46 drivers/regulator/irq_helpers.c > > 43 > 44 static void die_loudly(const char *msg) > 45 { > > 46 pr_emerg(msg); > 47 BUG(); > 48 } > 49 Best Regards Matti Vaittinen
next prev parent reply other threads:[~2021-04-06 10:57 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 7:12 [PATCH v4 0/7] Extend regulator notification support Matti Vaittinen 2021-04-06 7:12 ` [PATCH v4 1/7] dt_bindings: Add protection limit properties Matti Vaittinen 2021-04-06 7:12 ` [PATCH v4 2/7] regulator: add warning flags Matti Vaittinen 2021-04-06 7:13 ` [PATCH v4 3/7] regulator: IRQ based event/error notification helpers Matti Vaittinen 2021-04-06 10:27 ` kernel test robot 2021-04-06 10:27 ` kernel test robot 2021-04-06 10:57 ` Matti Vaittinen [this message] 2021-04-06 10:57 ` Matti Vaittinen 2021-04-06 12:08 ` kernel test robot 2021-04-06 12:08 ` kernel test robot [not found] ` <CAHp75VeoTVNDemV0qRA4BTVqOVfyR9UKGWhHgfeat8zVVGcu_Q@mail.gmail.com> 2021-04-07 5:02 ` Matti Vaittinen 2021-04-07 9:10 ` Andy Shevchenko 2021-04-07 9:49 ` Vaittinen, Matti 2021-04-07 12:50 ` Andy Shevchenko 2021-04-09 3:20 ` Kees Cook 2021-04-09 7:08 ` Vaittinen, Matti 2021-04-12 12:24 ` Matti Vaittinen 2021-04-12 13:09 ` Mark Brown 2021-04-06 7:13 ` [PATCH v4 4/7] regulator: add property parsing and callbacks to set protection limits Matti Vaittinen 2021-04-06 7:14 ` [PATCH v4 5/7] dt-bindings: regulator: bd9576 add FET ON-resistance for OCW Matti Vaittinen 2021-04-06 7:14 ` [PATCH v4 6/7] regulator: bd9576: Support error reporting Matti Vaittinen 2021-04-06 7:16 ` [PATCH v4 7/7] regulator: bd9576: Fix the driver name in id table Matti Vaittinen
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=7706d59fe7120106e4695fd83da5b089d5a36d87.camel@fi.rohmeurope.com \ --to=matti.vaittinen@fi.rohmeurope.com \ --cc=agross@kernel.org \ --cc=bjorn.andersson@linaro.org \ --cc=broonie@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=kbuild-all@lists.01.org \ --cc=lgirdwood@gmail.com \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-power@fi.rohmeurope.com \ --cc=lkp@intel.com \ --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.