From: Takashi Iwai <tiwai@suse.de>
To: "Jani Nikula" <jani.nikula@linux.intel.com>
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
"Dave Airlie" <airlied@gmail.com>, <bhelgaas@google.com>,
<perex@perex.cz>, <mst@redhat.com>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
"Gerd Hoffmann" <kraxel@redhat.com>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: QEMU top-level IDs for (sub)vendor & device
Date: Fri, 29 Jan 2016 10:45:41 +0100 [thread overview]
Message-ID: <s5hlh78lnwa.wl-tiwai@suse.de> (raw)
In-Reply-To: <87powkiwqp.fsf@intel.com>
On Fri, 29 Jan 2016 10:02:54 +0100,
Jani Nikula wrote:
>
>
> This one's lacking some maintainers, adding for acks. There's already
> review from Gerd [1], and seems like a good idea anyway.
Feel free to take my ack, too
Reviewed-by: Takashi Iwai <tiwai@suse.de>
thanks,
Takashi
prev parent reply other threads:[~2016-01-29 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1453739846-3549-1-git-send-email-robbat2@gentoo.org>
2016-01-29 9:02 ` [PATCH] PCI: QEMU top-level IDs for (sub)vendor & device Jani Nikula
2016-01-29 9:45 ` 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=s5hlh78lnwa.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=airlied@gmail.com \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=perex@perex.cz \
--cc=robbat2@gentoo.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