mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>, Mark Brown <broonie@kernel.org>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound updates for 4.5-rc1
Date: Mon, 18 Jan 2016 07:26:56 +0100	[thread overview]
Message-ID: <s5hd1szs8r3.wl-tiwai@suse.de> (raw)
In-Reply-To: <CA+55aFw__OT4tzsKhHt2QXViQ-j-q6V6149U2XLiuvaDjY31eA@mail.gmail.com>

On Sun, 17 Jan 2016 22:15:41 +0100,
Linus Torvalds wrote:
> 
> On Sat, Jan 16, 2016 at 8:03 AM, Takashi Iwai <tiwai@suse.de> wrote:
> >
> > [NOTE: this contains also many commits for DRM.  This is due to the
> >  pull of drm stable branch into sound tree, as the base of i915 audio
> >  component work for HD-audio.  The highlights below don't contain
> >  these DRM changes, as these are supposed to be pulled via drm tree in
> >  anyway sooner or later.]
> 
> The drm parts also introduce a new warning:
> 
>   drivers/gpu/drm/i915/intel_display.c:5232:0: warning:
> "for_each_power_domain" redefined
>   drivers/gpu/drm/i915/i915_drv.h:312:0: note: this is the location of
> the previous definition
> 
> which I'm leaving alone because I'm hoping that it will just magically
> fix itself when I get the full drm pull.

Oh yes, I should have mentioned it.  It's intermittent and the fix is
in drm tree.

> But I wanted to mention it, just to make sure that it _does_ get fixed.

Thanks!


Takashi

      reply	other threads:[~2016-01-18  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 16:03 Takashi Iwai
2016-01-17 21:15 ` Linus Torvalds
2016-01-18  6:26   ` 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=s5hd1szs8r3.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=airlied@gmail.com \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®