Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1674931 > unrolled thread
| Started by | John Stultz <john.stultz@linaro.org> |
|---|---|
| First post | 2017-06-26 18:40 +0200 |
| Last post | 2017-06-28 21:30 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id John Stultz <john.stultz@linaro.org> - 2017-06-26 18:40 +0200
Re: [PATCH] drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id Mark Brown <broonie@kernel.org> - 2017-06-28 21:30 +0200
| From | John Stultz <john.stultz@linaro.org> |
|---|---|
| Date | 2017-06-26 18:40 +0200 |
| Subject | Re: [PATCH] drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id |
| Message-ID | <tWFdo-4I2-21@gated-at.bofh.it> |
On Tue, Jun 13, 2017 at 5:05 PM, Mark Brown <broonie@kernel.org> wrote: > On Tue, Jun 13, 2017 at 02:59:49PM -0700, John Stultz wrote: >> ALSA SoC needs to know connected DAI ID for probing. Using >> the new audio-card-graph approach, ports/endpoints are used >> to describe how the links are connected. Unfortunately, since > > Unless someone objects in the next week or so I intend to apply this. Hey Mark, Just wanted to check on this to make sure it didn't slip by. I've not seen it show up in -next yet. thanks -john
[toc] | [next] | [standalone]
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Date | 2017-06-28 21:30 +0200 |
| Message-ID | <tXqP0-1wb-25@gated-at.bofh.it> |
| In reply to | #1674931 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Jun 26, 2017 at 09:31:34AM -0700, John Stultz wrote: > Hey Mark, > Just wanted to check on this to make sure it didn't slip by. I've > not seen it show up in -next yet. Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, attend conferences and so on so unless there is some reason for urgency (like critical bug fixes) please allow at least a couple of weeks for review. If there have been review comments then people may be waiting for those to be addressed. Sending content free pings just adds to the mail volume (if they are seen at all) and if something has gone wrong you'll have to resend the patches anyway.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web