From: Davidlohr Bueso <dave@stgolabs.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, eric@anholt.net, wahrenst@gmx.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vc04_services: replace g_free_fragments_mutex with spinlock
Date: Mon, 28 Oct 2019 09:35:37 -0700 [thread overview]
Message-ID: <20191028163537.b2pspgdl6ceevcxv@linux-p48b> (raw)
In-Reply-To: <20191028162412.GA321492@kroah.com>
On Mon, 28 Oct 2019, Greg KH wrote:
>This is obviously not in a format I can apply it in :(
What are you talking about? I sent you the original patch,
then Cc'ed the drivers mailing list. So you still have a
patch you can apply... this is quite a common way of doing
things (Ccing for future references to someone or another
ml). I don't understand why you are hairsplitting over this
patch.
Thanks,
Davidlohr
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2019-10-28 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191027221530.12080-1-dave@stgolabs.net>
[not found] ` <576df522-f012-9dd1-9dcc-b7e444e82ac6@gmx.net>
2019-10-28 15:21 ` [PATCH] staging: vc04_services: replace g_free_fragments_mutex with spinlock Davidlohr Bueso
2019-10-28 15:37 ` Greg KH
2019-10-28 15:53 ` Davidlohr Bueso
2019-10-28 16:24 ` Greg KH
2019-10-28 16:35 ` Davidlohr Bueso [this message]
2019-10-28 16:59 ` Greg KH
2019-11-01 18:29 ` [PATCH resend] " Davidlohr Bueso
2019-11-02 10:33 ` Stefan Wahren
2019-11-02 10:35 ` Greg KH
2019-10-28 19:08 ` [PATCH] " Dan Carpenter
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=20191028163537.b2pspgdl6ceevcxv@linux-p48b \
--to=dave@stgolabs.net \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wahrenst@gmx.net \
/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).