From: Mario Limonciello <mario_limonciello@dell.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/1] Backport Dell XPS 13 (2015) HDA microphone support to v4.0.y
Date: Tue, 28 Apr 2015 16:55:14 -0500 [thread overview]
Message-ID: <554001C2.4050406@dell.com> (raw)
In-Reply-To: <20150428200415.GB31191@kroah.com>
On 04/28/2015 03:04 PM, Greg KH wrote:
> On Tue, Apr 28, 2015 at 11:13:28AM -0500, Mario Limonciello wrote:
>> I didn't see an ACK or NACK on these 3 patches (4.0.y, 3.19.y, and 3.18.y).
> They are behind about 100+ other patches I need to get to for the 4.0
> and 3.19 kernels, please be patient.
>
> thanks,
>
> greg k-h
Oh I didn't realize that. I was worried since I submitted actual patches rather than submitting commits that I did something wrong. I'll shut up and wait.
next prev parent reply other threads:[~2015-04-28 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1429655102-4494-1-git-send-email-mario_limonciello@dell.com>
2015-04-28 16:13 ` [PATCH 1/1] Backport Dell XPS 13 (2015) HDA microphone support to v4.0.y Mario Limonciello
2015-04-28 20:04 ` Greg KH
2015-04-28 21:55 ` Mario Limonciello [this message]
2015-04-28 22:09 ` 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=554001C2.4050406@dell.com \
--to=mario_limonciello@dell.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox