From: Takashi Iwai <tiwai@suse.de>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Jim Qu <Jim.Qu@amd.com>,
alsa-devel@alsa-project.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Split audio component to a generic type
Date: Mon, 16 Jul 2018 19:50:48 +0200 [thread overview]
Message-ID: <s5hefg3kr2f.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180716172216.GE4262@intel.com>
On Mon, 16 Jul 2018 19:22:17 +0200,
Rodrigo Vivi wrote:
>
> > --- /dev/null
> > +++ b/include/drm/drm_audio_component.h
> > @@ -0,0 +1,115 @@
> > +/*
> > + * Copyright © 2014 Intel Corporation
> > + *
> > + * Permission is hereby granted, free of charge, to any person obtaining a
> > + * copy of this software and associated documentation files (the "Software"),
> > + * to deal in the Software without restriction, including without limitation
> > + * the rights to use, copy, modify, merge, publish, distribute, sublicense,
> > + * and/or sell copies of the Software, and to permit persons to whom the
> > + * Software is furnished to do so, subject to the following conditions:
> > + *
> > + * The above copyright notice and this permission notice (including the next
> > + * paragraph) shall be included in all copies or substantial portions of the
> > + * Software.
> > + *
> > + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
> > + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> > + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
> > + * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> > + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> > + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
> > + * IN THE SOFTWARE.
> > + */
>
> I think it is better to start new files with SPDX identifiers....
Yeah, it's a more sensible option. Will rewrite in v2.
> > +
> > +#ifndef _DRM_AUDIO_COMPONENT_H_
> > +#define _DRM_AUDIO_COMPONENT_H_
> > +
> > +/**
> > + * struct drm_audio_component_ops - Ops implemented by DRM driver, called by hda driver
> > + */
> > +struct drm_audio_component_ops {
> > + /**
> > + * @owner: i915 module
>
> drm now?
Right. Will be fixed in v2, too.
Thanks!
Takashi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-07-16 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 13:48 [PATCH 0/3] Make the audio component binding more generic Takashi Iwai
2018-07-16 13:48 ` [PATCH 1/3] drm/i915: Split audio component to a generic type Takashi Iwai
2018-07-16 17:22 ` [Intel-gfx] " Rodrigo Vivi
2018-07-16 17:50 ` Takashi Iwai [this message]
2018-07-16 20:35 ` Takashi Iwai
2018-07-16 13:48 ` [PATCH 2/3] ALSA: hda/i915: Associate audio component with devres Takashi Iwai
2018-07-16 13:48 ` [PATCH 3/3] ALSA: hda: Make audio component support more generic Takashi Iwai
2018-07-16 20:33 ` Takashi Iwai
2018-07-16 19:02 ` ✗ Fi.CI.BAT: failure for Make the audio component binding " Patchwork
2018-07-17 6:34 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
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=s5hefg3kr2f.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Jim.Qu@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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 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.