[alsa-devel] [GIT PULL] soundwire updates for v5.2-rc1
Hey Greg,
Please PULL to receive updates to soundwire subsystem
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-5.2-rc1
for you to fetch changes up to 4abbd783d126cabfc20d1b8d50b1d5026b5cba09:
soundwire: intel: fix implicit header use of module.h/export.h (2019-04-14 15:52:50 +0530)
---------------------------------------------------------------- soundwire updates for v5.2-rc1
This round saw interest from Intel, Linaro and Cadence in Soundwire. More patches are in pipeline (maybe next cycle)
- removal of useless initialzation in core - couple of header and kcalloc inversion fixes on Intel driver
---------------------------------------------------------------- Paul Gortmaker (1): soundwire: intel: fix implicit header use of module.h/export.h
Pierre-Louis Bossart (3): soundwire: intel: fix inversion in devm_kcalloc parameters soundwire: remove useless initializations soundwire: stream: remove useless initialization of local variable
drivers/soundwire/bus.c | 2 -- drivers/soundwire/intel.c | 5 +++-- drivers/soundwire/intel_init.c | 2 ++ drivers/soundwire/stream.c | 2 +- 4 files changed, 6 insertions(+), 5 deletions(-)
Thanks
On Mon, Apr 29, 2019 at 04:58:29PM +0530, Vinod Koul wrote:
Hey Greg,
Please PULL to receive updates to soundwire subsystem
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-5.2-rc1
Pulled and pushed out, thanks,
greg k-h
On 29-04-19, 13:43, Greg KH wrote:
On Mon, Apr 29, 2019 at 04:58:29PM +0530, Vinod Koul wrote:
Hey Greg,
Please PULL to receive updates to soundwire subsystem
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-5.2-rc1
Pulled and pushed out, thanks,
That was fast :)
Thanks
On 4/29/19 6:46 AM, Vinod Koul wrote:
On 29-04-19, 13:43, Greg KH wrote:
On Mon, Apr 29, 2019 at 04:58:29PM +0530, Vinod Koul wrote:
Hey Greg,
Please PULL to receive updates to soundwire subsystem
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-5.2-rc1
Pulled and pushed out, thanks,
That was fast :)
Vinod, is there any reason why you didn't take the rest of my clean-up patches? The feedback you provided wasn't really relevant (patches do apply and alignment is fine) and you didn't reply to my questions. That's not 'fast'. If we start having such delays with trivial patches, I can only imagine how well this is going to work with the rest of the patches I am cooking... Regards -Pierre
On 29-04-19, 07:53, Pierre-Louis Bossart wrote:
On 4/29/19 6:46 AM, Vinod Koul wrote:
On 29-04-19, 13:43, Greg KH wrote:
On Mon, Apr 29, 2019 at 04:58:29PM +0530, Vinod Koul wrote:
Hey Greg,
Please PULL to receive updates to soundwire subsystem
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-5.2-rc1
Pulled and pushed out, thanks,
That was fast :)
Vinod, is there any reason why you didn't take the rest of my clean-up patches? The feedback you provided wasn't really relevant (patches do apply and alignment is fine) and you didn't reply to my questions.
Sorry I though base don comments a v2 was coming, I will recheck and see if there is anything pending from my side. Nevertheless whats gets into a PULL request is frozen some days back, even if I had applied afterwards chances are that it wont have gone into this one. But hey there is always next one...
That's not 'fast'. If we start having such delays with trivial patches, I can only imagine how well this is going to work with the rest of the patches I am cooking...
I never claim to be as fast as Greg :) But delays will be there, without seeing rest of the patches I cant comment. But yes you can make it easy for people to review which ensures they get done faster
Anyway lets discuss those points in relevant threads.
Thanks
participants (3)
-
Greg KH -
Pierre-Louis Bossart -
Vinod Koul