From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: vkoul@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
pierre-louis.bossart@linux.intel.com
Subject: Re: [GIT PULL] SoundWire updates for 4.20-rc1
Date: Wed, 3 Oct 2018 23:48:15 +0200 [thread overview]
Message-ID: <CANiq72kY-f+tpOFOsG5VcK5z9W4LsCBmibtxJx4h=UTLQMd6oA@mail.gmail.com> (raw)
In-Reply-To: <20181002184400.GA28146@kroah.com>
Hi Greg,
On Tue, Oct 2, 2018 at 8:44 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Oct 02, 2018 at 08:38:41PM +0200, Miguel Ojeda wrote:
> > Hi Greg,
> >
> > On Tue, Oct 2, 2018 at 8:20 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Tue, Oct 02, 2018 at 07:53:27PM +0530, Vinod wrote:
> > > > Hey Greg,
> > > >
> > > > Here are the SoundWire updates (again) for 4.20-rc1/5.0-rc1
> > > > This brings in the multi-link streaming support and rst format
> > > > corrections. The changes are in linux-next for quite some time.
> > > >
> > > > Please consider pull to receive:
> > > >
> > > > The following changes since commit 8d6ccf5cebbc7ed1dee9986e36853a78dfb64084:
> > > >
> > > > soundwire: Fix acquiring bus lock twice during master release (2018-08-27 09:49:48 +0530)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-4.20-rc1
> > >
> > > Now pulled, thanks.
> > >
> > > greg k-h
> >
> > Confused here -- pulled to where? 4.19 will still have rc7, no?
>
> Pulled to my char-misc-branch to be submitted to "mainline" once
> 4.19-final is out.
Ah, alright! Sorry & thanks!
>
> This has nothing to do with the 4.19-rc development process right now,
> sorry for any potential confusion.
No problem! It was bound to happen now that you are Linus' alter ego ;-)
Cheers,
Miguel
prev parent reply other threads:[~2018-10-03 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 14:23 [GIT PULL] SoundWire updates for 4.20-rc1 Vinod
2018-10-02 16:38 ` Greg KH
2018-10-02 18:38 ` Miguel Ojeda
2018-10-02 18:44 ` Greg KH
2018-10-03 21:48 ` Miguel Ojeda [this message]
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='CANiq72kY-f+tpOFOsG5VcK5z9W4LsCBmibtxJx4h=UTLQMd6oA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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 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).