From: Ladislav Michl <ladis@linux-mips.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: Re: [PATCH 3/6] ASoC: max9867: Drop probe function
Date: Thu, 1 Mar 2018 21:06:18 +0100 [thread overview]
Message-ID: <20180301200618.GB2304@lenoch> (raw)
In-Reply-To: <20180301175654.GF12864@sirena.org.uk>
On Thu, Mar 01, 2018 at 05:56:54PM +0000, Mark Brown wrote:
> On Thu, Mar 01, 2018 at 03:20:27PM +0100, Ladislav Michl wrote:
> > Driver probe function has no use and can be deleted.
>
> This doesn't apply against current code, please check and resend.
It was generated and tested against next-20180301. Which version do
you want me to generate against? Based on 4.16-rc1 it'll fail to
merge later.
Thank you,
ladis
next prev parent reply other threads:[~2018-03-01 20:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 14:18 [PATCH 0/6] ASoC: max9867: Driver update Ladislav Michl
2018-03-01 14:19 ` [PATCH 1/6] ASoC: max9867: Show Kconfig entry Ladislav Michl
2018-03-01 14:19 ` [PATCH 2/6] ASoC: max9867: Improve error logging Ladislav Michl
2018-03-01 18:06 ` Applied "ASoC: max9867: Improve error logging" to the asoc tree Mark Brown
2018-03-01 14:20 ` [PATCH 3/6] ASoC: max9867: Drop probe function Ladislav Michl
2018-03-01 17:56 ` Mark Brown
2018-03-01 20:06 ` Ladislav Michl [this message]
2018-03-01 20:39 ` Mark Brown
2018-03-01 21:32 ` Ladislav Michl
2018-03-01 21:37 ` Mark Brown
2018-03-02 13:17 ` Applied "ASoC: max9867: Drop probe function" to the asoc tree Mark Brown
2018-03-01 14:20 ` [PATCH 4/6] ASoC: max9867: Fix codec capabilities Ladislav Michl
2018-03-01 18:06 ` Applied "ASoC: max9867: Fix codec capabilities" to the asoc tree Mark Brown
2018-03-01 14:21 ` [PATCH 5/6] ASoC: max9867: DSP mode Ladislav Michl
2018-03-01 18:06 ` Applied "ASoC: max9867: DSP mode" to the asoc tree Mark Brown
2018-03-01 14:22 ` [PATCH 6/6] ASoC: max9867: Use continuous sample rate Ladislav Michl
2018-03-01 18:22 ` Mark Brown
2018-03-01 21:47 ` Ladislav Michl
2018-03-02 10:50 ` 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=20180301200618.GB2304@lenoch \
--to=ladis@linux-mips.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@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 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.