All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod <vkoul@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [GIT PULL] soundwire updates for v4.19-rc1
Date: Wed, 12 Sep 2018 14:52:33 +0530	[thread overview]
Message-ID: <20180912092233.GG2766@vkoul-mobl> (raw)
In-Reply-To: <20180912072945.GA24289@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

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?

Thanks
-- 
~Vinod

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2018-09-12  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 16:28 [GIT PULL] soundwire updates for v4.19-rc1 Vinod
2018-09-12  7:29 ` Greg KH
2018-09-12  9:22   ` Vinod [this message]
2018-09-12 18:19     ` Greg KH

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=20180912092233.GG2766@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    /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.