From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>, Greg KH <gregkh@linuxfoundation.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [GIT PULL] soundwire updates for v5.2-rc1
Date: Mon, 29 Apr 2019 07:53:05 -0500 [thread overview]
Message-ID: <24c3eef6-2a91-afbd-04f1-2e9a0db29f1c@linux.intel.com> (raw)
In-Reply-To: <20190429114617.GJ3845@vkoul-mobl.Dlink>
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
next prev parent reply other threads:[~2019-04-29 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 11:28 [GIT PULL] soundwire updates for v5.2-rc1 Vinod Koul
2019-04-29 11:43 ` Greg KH
2019-04-29 11:46 ` Vinod Koul
2019-04-29 12:53 ` Pierre-Louis Bossart [this message]
2019-04-30 8:42 ` 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=24c3eef6-2a91-afbd-04f1-2e9a0db29f1c@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.org \
--cc=vkoul@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.