[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180912181928.GA15480@kroah.com>
Date: Wed, 12 Sep 2018 20:19:28 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Vinod <vkoul@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Subject: Re: [GIT PULL] soundwire updates for v4.19-rc1
On Wed, Sep 12, 2018 at 02:52:33PM +0530, Vinod wrote:
> On 12-09-18, 09:29, Greg KH wrote:
> > On Wed, Aug 08, 2018 at 09:58:50PM +0530, Vinod wrote:
> > > Hey Greg,
> > >
> > > Please PULL to receive the soundwire update for v4.19-rc1 with a signed
> > > tag as you requested last time and the norm :-)
> > >
> > > The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
> > >
> > > Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/soundwire.git tags/soundwire-4.19-rc1
> >
> > It's too late for all of these patches to go into 4.19-final. Can you
> > split this up into two sets of patches? One for bugfixes to get into
> > 4.19-final and one for new features for 4.20-rc1?
>
> Yeah to be fair these were posted a bit late as well. I have already
> rebased these on top of 4.19-rc1 and had them included in the linux-next
> as well.
>
> I will send fixes tag now. Would -rc6 be apt time for 4.20-rc1
> inclusions?
Yes, that's fine, but you can always send things sooner if you have
them.
thanks,
greg k-h
Powered by blists - more mailing lists