Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH v6 1/2] PCI: Add a helper to check Power Resource Requirements _PR3 existence
Date: Mon, 21 Oct 2019 15:15:14 +0200	[thread overview]
Message-ID: <s5hv9sidyu5.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hlftih26g.wl-tiwai@suse.de>

On Fri, 18 Oct 2019 10:45:43 +0200,
Takashi Iwai wrote:
> 
> On Fri, 18 Oct 2019 10:30:11 +0200,
> Kai-Heng Feng wrote:
> > 
> > 
> > 
> > > On Oct 18, 2019, at 16:18, Takashi Iwai <tiwai@suse.de> wrote:
> > > 
> > > On Fri, 18 Oct 2019 09:38:47 +0200,
> > > Kai-Heng Feng wrote:
> > >> 
> > >> A driver may want to know the existence of _PR3, to choose different
> > >> runtime suspend behavior. A user will be add in next patch.
> > >> 
> > >> This is mostly the same as nouveau_pr3_present().
> > >> 
> > >> Reported-by: kbuild test robot <lkp@intel.com>
> > > 
> > > It's confusing -- this particular change isn't reported by the test
> > > bot, but only about the lack of the CONFIG_ACPI ifdef.
> > 
> > Hmm, because the test bot asked to add the tag.
> 
> Yes, but it's only if you add a new fix patch on top of it.
> You can write some their credit, too, but basically it'd be enough to
> point to the Link tag to the thread.
> 
> > If it's not appropriate will you drop it? I can also send a v7.
> 
> I can modify in my side.

Now I merged both patches to for-next branch.


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2019-10-21 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  7:38 [alsa-devel] [PATCH v6 1/2] PCI: Add a helper to check Power Resource Requirements _PR3 existence Kai-Heng Feng
2019-10-18  7:38 ` [alsa-devel] [PATCH v6 2/2] ALSA: hda: Allow HDA to be runtime suspended when dGPU is not bound to a driver Kai-Heng Feng
2020-01-10  9:43   ` Jaroslav Kysela
2020-01-10  9:56     ` Takashi Iwai
2020-01-10 10:31       ` Jaroslav Kysela
2019-10-18  8:18 ` [alsa-devel] [PATCH v6 1/2] PCI: Add a helper to check Power Resource Requirements _PR3 existence Takashi Iwai
2019-10-18  8:30   ` Kai-Heng Feng
2019-10-18  8:45     ` Takashi Iwai
2019-10-21 13:15       ` 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=s5hv9sidyu5.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhelgaas@google.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.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: 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