All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org,
	Rakesh Ughreja <rakesh.a.ughreja@intel.com>,
	kbuild test robot <lkp@intel.com>,
	kbuild-all@01.org
Subject: Re: [asoc:for-4.20 333/424] sound/pci/hda/patch_ca0132.c:7650:20: error: implicit declaration of function 'pci_iomap'; did you mean 'pcim_iomap'?
Date: Wed, 12 Sep 2018 11:41:45 +0100	[thread overview]
Message-ID: <20180912104145.GE6062@sirena.org.uk> (raw)
In-Reply-To: <s5h4lew34fv.wl-tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 368 bytes --]

On Tue, Sep 11, 2018 at 08:59:16AM +0200, Takashi Iwai wrote:

> I can fix it in my side, but the problem is that the change isn't
> pulled into my tree yet.  So it must be fixed in Mark's tree, or Mark
> send a pull request including this change and let me fix it.

I'll just apply a fix.  I was kind of hoping the Intel people would care
about this but guess not :(

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-09-12 10:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  5:29 [asoc:for-4.20 333/424] sound/pci/hda/patch_ca0132.c:7650:20: error: implicit declaration of function 'pci_iomap'; did you mean 'pcim_iomap'? kbuild test robot
2018-09-11  6:59 ` Takashi Iwai
2018-09-12 10:41   ` Mark Brown [this message]
2018-09-12 11:31   ` Mark Brown
2018-09-12 12:01     ` Takashi Iwai
2018-09-12 12:04       ` Mark Brown
2018-10-22 17:44         ` Pierre-Louis Bossart
2018-10-23 10:00           ` Mark Brown

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=20180912104145.GE6062@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=kbuild-all@01.org \
    --cc=lkp@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rakesh.a.ughreja@intel.com \
    --cc=tiwai@suse.de \
    /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.