From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [plbossart-sound:integration/soundwire-intel 26/52] drivers/soundwire/intel_init.c:214:5: error: 'struct sdw_intel_ctx' has no member named 'irq'
Date: Thu, 05 Dec 2019 19:17:32 +0800 [thread overview]
Message-ID: <201912051900.nclbO2er%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3367 bytes --]
tree: https://github.com/plbossart/sound integration/soundwire-intel
head: 48a6255c085fe193ab7005f7804d2a06eca23ae2
commit: b03683a8fed50d5d81af9e17cfef5188968d362e [26/52] soundwire: intel/cadence: merge Soundwire interrupt handlers/threads
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-1) 7.5.0
reproduce:
git checkout b03683a8fed50d5d81af9e17cfef5188968d362e
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/soundwire/intel_init.c: In function 'sdw_intel_probe_controller':
>> drivers/soundwire/intel_init.c:214:5: error: 'struct sdw_intel_ctx' has no member named 'irq'
ctx->irq = res->irq;
^~
vim +214 drivers/soundwire/intel_init.c
178
179 static struct sdw_intel_ctx
180 *sdw_intel_probe_controller(struct sdw_intel_res *res)
181 {
182 struct sdw_intel_link_res *link;
183 struct sdw_intel_ctx *ctx;
184 struct acpi_device *adev;
185 struct sdw_master_device *md;
186 u32 link_mask;
187 int count;
188 int i;
189
190 if (!res)
191 return NULL;
192
193 if (acpi_bus_get_device(res->handle, &adev))
194 return NULL;
195
196 if (!res->count)
197 return NULL;
198
199 count = res->count;
200 dev_dbg(&adev->dev, "Creating %d SDW Link devices\n", count);
201
202 ctx = kzalloc(sizeof(*ctx), GFP_KERNEL);
203 if (!ctx)
204 return NULL;
205
206 ctx->links = kcalloc(count, sizeof(*ctx->links), GFP_KERNEL);
207 if (!ctx->links)
208 goto link_err;
209
210 ctx->count = count;
211 ctx->mmio_base = res->mmio_base;
212 ctx->link_mask = res->link_mask;
213 ctx->handle = res->handle;
> 214 ctx->irq = res->irq;
215
216 link = ctx->links;
217 link_mask = ctx->link_mask;
218
219 INIT_LIST_HEAD(&ctx->link_list);
220
221 /* Create SDW Master devices */
222 for (i = 0; i < count; i++, link++) {
223 if (link_mask && !(link_mask & BIT(i)))
224 continue;
225
226 md = sdw_md_add(&intel_sdw_driver,
227 res->parent,
228 acpi_fwnode_handle(adev),
229 i);
230
231 if (IS_ERR(md)) {
232 dev_err(&adev->dev, "Could not create link %d\n", i);
233 goto err;
234 }
235 link->md = md;
236 link->mmio_base = res->mmio_base;
237 link->registers = res->mmio_base + SDW_LINK_BASE
238 + (SDW_LINK_SIZE * i);
239 link->shim = res->mmio_base + SDW_SHIM_BASE;
240 link->alh = res->mmio_base + SDW_ALH_BASE;
241 link->ops = res->ops;
242 link->dev = res->dev;
243
244 /* let the SoundWire master driver to its probe */
245 md->driver->probe(md, link);
246
247 list_add_tail(&link->list, &ctx->link_list);
248 }
249
250 return ctx;
251
252 err:
253 sdw_intel_cleanup(ctx);
254 link_err:
255 kfree(ctx);
256 return NULL;
257 }
258
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 70303 bytes --]
reply other threads:[~2019-12-05 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201912051900.nclbO2er%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.