All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: stable@vger.kernel.org,
	Jaska Uimonen <jaska.uimonen@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: SOF: intel: hda: support also devices with 1 and 3 dmics
Date: Mon, 21 Sep 2020 18:21:59 +0200	[thread overview]
Message-ID: <20200921162159.GA1260133@kroah.com> (raw)
In-Reply-To: <399fe98f-5577-6616-8539-885cbc89be1b@linux.intel.com>

On Mon, Sep 21, 2020 at 11:18:47AM -0500, Pierre-Louis Bossart wrote:
> 
> 
> On 9/21/20 11:10 AM, Greg KH wrote:
> > On Fri, Sep 18, 2020 at 11:15:33AM -0500, Pierre-Louis Bossart wrote:
> > > From: Jaska Uimonen <jaska.uimonen@linux.intel.com>
> > > 
> > > [ Backported from Upstream commit 3dca35e35b42b3405ddad7ee95c02a2d8cf28592]
> > 
> > There is no such commit in Linus's tree :(
> 
> no such commit yet, it's in Mark Brown's tree and should be in 5.10
> 
> https://lore.kernel.org/alsa-devel/20200825235040.1586478-4-ranjani.sridharan@linux.intel.com/
> 
> I must admit I didn't know how to tweak the information between brackets.
> 
> do you want me to remove the 'Upstream' comment and resend?

I can't take anything that is not already in Linus's tree, so we need to
wait until it hits there, right?

thanks,

greg k-h

  reply	other threads:[~2020-09-21 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 16:15 [PATCH] ASoC: SOF: intel: hda: support also devices with 1 and 3 dmics Pierre-Louis Bossart
2020-09-21 16:10 ` Greg KH
2020-09-21 16:18   ` Pierre-Louis Bossart
2020-09-21 16:21     ` Greg KH [this message]
2020-09-21 16:33       ` Pierre-Louis Bossart

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=20200921162159.GA1260133@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=jaska.uimonen@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=stable@vger.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.