From: Greg KH <gregkh@linuxfoundation.org>
To: David Matlack <matlackdavid@gmail.com>
Cc: devel@driverdev.osuosl.org, charrer@alacritech.com,
linux-kernel@vger.kernel.org, Lior Dotan <liodot@gmail.com>
Subject: Re: [PATCH] staging: slicoss: remove private netdev list
Date: Sat, 24 May 2014 07:17:21 +0900 [thread overview]
Message-ID: <20140523221721.GA17876@kroah.com> (raw)
In-Reply-To: <CANoiuG+=V9o6Ui2vmDPj21+tB7jFX87r8fgeDB8d7DYAbzZC9Q@mail.gmail.com>
On Fri, May 23, 2014 at 01:11:01PM -0700, David Matlack wrote:
> Greg, this is one of the two patches that got dropped. It should apply cleanly
> in any order with respect to all my other patches.
As my patch queue is now flushed out, what is "this" patch? :)
Can you please just resend the two missing patches?
thanks,
greg k-h
next prev parent reply other threads:[~2014-05-23 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 4:25 [PATCH] staging: slicoss: fix use-after-free in slic_entry_probe David Matlack
2014-05-23 4:25 ` [PATCH] staging: slicoss: fix free-after-free in slic_entry_remove David Matlack
2014-05-23 4:25 ` [PATCH] staging: slicoss: remove unused members of struct adapter David Matlack
2014-05-23 4:25 ` [PATCH] staging: slicoss: remove gratuitous debug infrastructure David Matlack
2014-05-23 4:25 ` [PATCH] staging: slicoss: fix 64-bit isr address bug David Matlack
2014-05-23 4:25 ` [PATCH] staging: slicoss: fix use-after-free bug in slic_entry_remove David Matlack
2014-05-23 4:25 ` [PATCH] staging: slicoss: remove private netdev list David Matlack
2014-05-23 20:11 ` David Matlack
2014-05-23 22:17 ` Greg KH [this message]
2014-05-23 4:25 ` [PATCH] staging: slicoss: clean up use of dev_err David Matlack
2014-05-23 20:14 ` David Matlack
2014-05-23 11:14 ` [PATCH] staging: slicoss: fix use-after-free in slic_entry_probe Greg KH
2014-05-23 20:07 ` David Matlack
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=20140523221721.GA17876@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=charrer@alacritech.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@gmail.com \
--cc=matlackdavid@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox