From: Ross Zwisler <zwisler@google.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ross Zwisler <zwisler@chromium.org>,
Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [linux-4.4.y PATCH] ASoC: Intel: avoid Oops if DMA setup fails
Date: Thu, 9 May 2019 12:11:05 -0600 [thread overview]
Message-ID: <20190509181105.GA43688@google.com> (raw)
In-Reply-To: <20190509174147.GA17342@kroah.com>
On Thu, May 09, 2019 at 07:41:47PM +0200, Greg KH wrote:
> On Sun, May 05, 2019 at 03:15:53PM +0200, Greg KH wrote:
> > On Fri, May 03, 2019 at 01:45:03PM -0600, Ross Zwisler wrote:
> > > From: Ross Zwisler <zwisler@chromium.org>
> > >
> > > commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream.
> >
> > This commit id is not in Linus's tree :(
> >
>
> Sorry for the noise, I didn't read your note :(
No worries, sorry for sending early. I'll wait until after it's merged next
time. :) Thanks for pulling it in.
prev parent reply other threads:[~2019-05-09 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 16:47 [PATCH] ASoC: Intel: avoid Oops if DMA setup fails Ross Zwisler
2019-04-26 21:03 ` Pierre-Louis Bossart
2019-04-29 17:02 ` Ross Zwisler
2019-04-29 18:25 ` [PATCH v2] " Ross Zwisler
2019-04-29 18:45 ` Pierre-Louis Bossart
2019-05-03 4:34 ` Mark Brown
2019-05-03 6:18 ` Applied "ASoC: Intel: avoid Oops if DMA setup fails" to the asoc tree Mark Brown
2019-05-03 6:21 ` Mark Brown
2019-05-03 6:23 ` Mark Brown
[not found] ` <20190426185246.AD8E5206A3@mail.kernel.org>
2019-04-29 18:27 ` [PATCH] ASoC: Intel: avoid Oops if DMA setup fails Ross Zwisler
2019-05-03 19:45 ` [linux-4.4.y PATCH] " Ross Zwisler
2019-05-05 13:15 ` Greg KH
2019-05-09 17:41 ` Greg KH
2019-05-09 18:11 ` Ross Zwisler [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=20190509181105.GA43688@google.com \
--to=zwisler@google.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zwisler@chromium.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).