From: Vinod Koul <vinod.koul@intel.com>
To: Geliang Tang <geliangtang@163.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] ALSA: hdac: drop unused dev_to_hdac macro
Date: Mon, 4 Jan 2016 13:53:47 +0530 [thread overview]
Message-ID: <20160104082347.GG2940@localhost> (raw)
In-Reply-To: <b86ede48c70d4f57bb72d52045e4f2afe12a88ae.1451312334.git.geliangtang@163.com>
On Mon, Dec 28, 2015 at 10:47:11PM +0800, Geliang Tang wrote:
> dev_to_hdac is not used anymore so drop it.
No harm in keeping this for now as the systems using these will be coming
up and more users will be upstreamed...
>
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
> sound/hda/ext/hdac_ext_bus.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/sound/hda/ext/hdac_ext_bus.c b/sound/hda/ext/hdac_ext_bus.c
> index 2433f7c..58f6b98 100644
> --- a/sound/hda/ext/hdac_ext_bus.c
> +++ b/sound/hda/ext/hdac_ext_bus.c
> @@ -197,8 +197,6 @@ void snd_hdac_ext_bus_device_remove(struct hdac_ext_bus *ebus)
> }
> }
> EXPORT_SYMBOL_GPL(snd_hdac_ext_bus_device_remove);
> -#define dev_to_hdac(dev) (container_of((dev), \
> - struct hdac_device, dev))
>
> static inline struct hdac_ext_driver *get_edrv(struct device *dev)
> {
> --
> 2.5.0
>
>
--
~Vinod
next prev parent reply other threads:[~2016-01-04 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 14:47 [PATCH 1/4] ALSA: core: use dev_to_snd_card Geliang Tang
2015-12-28 14:47 ` [PATCH 2/4] ALSA: hdac: drop unused dev_to_hdac macro Geliang Tang
2016-01-04 8:23 ` Vinod Koul [this message]
2016-01-04 14:54 ` Geliang Tang
2015-12-28 14:47 ` [PATCH 3/4] ALSA: hdac: use dev_to_hdac_dev Geliang Tang
2016-01-04 8:21 ` Vinod Koul
2015-12-28 14:47 ` [PATCH 4/4] ASoC: hdac_hdmi: use dev_to_hdac_dev and to_ehdac_device Geliang Tang
2016-01-04 8:22 ` Vinod Koul
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=20160104082347.GG2940@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=geliangtang@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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