From: Lukas Wunner <lukas@wunner.de>
To: Mark Brown <broonie@kernel.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
"Fang, Yang A" <yang.a.fang@intel.com>,
alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH v2 1/1] ASoC: Intel: Use acpi_dev_present()
Date: Mon, 25 Jan 2016 22:13:58 +0100 [thread overview]
Message-ID: <20160125211358.GA10561@wunner.de> (raw)
In-Reply-To: <20160125154846.GV6588@sirena.org.uk>
Hi Mark,
On Mon, Jan 25, 2016 at 03:48:46PM +0000, Mark Brown wrote:
> On Thu, Jan 14, 2016 at 09:57:20PM +0100, Lukas Wunner wrote:
> > Use shiny new acpi_dev_present() and remove all the boilerplate
> > to search for a particular ACPI device. No functional change.
> > Cf. 2d12b6b381ba ("ACPI / utils: Add acpi_dev_present()").
> >
> > v2: Rebase on commit 95f098014815 ("ASoC: Intel: Move apci find
> > machine routines").
>
> As covered in SubmittingPatches don't include inter-version changelogs
> in the body of your commit log, put them after the ---. They are
> meaningless once the change is applied without the rest of the history.
I'm used to the drm and drm-intel practice of including the changelog
in the commit message, but will remember to move it to the git notes
when posting to alsa-devel in the future.
Thanks,
Lukas
next prev parent reply other threads:[~2016-01-25 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 20:57 [PATCH v2 0/1] ASoC: Intel: Use acpi_dev_present() Lukas Wunner
2016-01-14 20:57 ` [PATCH v2 1/1] " Lukas Wunner
2016-01-18 16:29 ` Vinod Koul
2016-01-25 15:48 ` Mark Brown
2016-01-25 21:13 ` Lukas Wunner [this message]
2016-01-27 13:32 ` Mark Brown
2016-01-27 18:37 ` Applied "ASoC: Intel: Use acpi_dev_present()" to the asoc tree Mark Brown
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=20160125211358.GA10561@wunner.de \
--to=lukas@wunner.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vinod.koul@intel.com \
--cc=yang.a.fang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).