From: Takashi Iwai <tiwai@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: alsa-devel@alsa-project.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [sound:topic/asus-e100h-4.10 5/26] arch/x86/include/asm/iosf_mbi.h:137:55: warning: 'struct notifier_block' declared inside parameter list will not be visible outside of this definition or declaration
Date: Fri, 24 Feb 2017 11:04:45 +0100 [thread overview]
Message-ID: <s5hr32n6h1e.wl-tiwai@suse.de> (raw)
In-Reply-To: <b7cefd0d-4933-32a2-f76a-63e51d51202a@redhat.com>
On Fri, 24 Feb 2017 10:24:27 +0100,
Hans de Goede wrote:
>
> Hi,
>
> I'm sending out a new v4 of the "coordinate cht i2c-pmic and i915-punit accesses"
> patch-set fixing this.
Thanks!
Just for avoid confusion: I'm keeping the patches in the branch only
for experiments, not meant for merge through my tree.
Takashi
prev parent reply other threads:[~2017-02-24 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 22:26 [sound:topic/asus-e100h-4.10 5/26] arch/x86/include/asm/iosf_mbi.h:137:55: warning: 'struct notifier_block' declared inside parameter list will not be visible outside of this definition or declaration kbuild test robot
2017-02-24 9:24 ` Hans de Goede
2017-02-24 10:04 ` Takashi Iwai [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=s5hr32n6h1e.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hdegoede@redhat.com \
/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