From: Michael Zoran <mzoran@crowfest.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, daniels@collabora.com,
linux-kernel@vger.kernel.org, eric@anholt.net,
noralf@tronnes.org, popcornmix@gmail.com
Subject: Re: [PATCH 1/2] staging: vc04_services: Fix unportable cast in vchiq_copy_from_user
Date: Mon, 24 Oct 2016 08:13:55 -0700 [thread overview]
Message-ID: <1477322035.2088.1.camel@crowfest.net> (raw)
In-Reply-To: <20161024144650.GE4469@mwanda>
At this point, I need to take a step back from this whole thing and
evaluate where this is all going. I started this arm64 thing for fun
as a tinker idea, and it is quickly becoming more then I think I want
to get involved with at this time.
I'm not saying I won't return to this at a later time or tinker with it
on my own. I just need to take a step back. I have sent out patches
and if someone else wants to use what I have submitted as a starting
point, that's completely fine with me.
Thanks.
On Mon, 2016-10-24 at 17:46 +0300, Dan Carpenter wrote:
> If you want to wait for someone else to take over that's fine. If
> you
> want to send a patch that's also fine. There is not really strict
> ownership of anything in the kernel. Greg will take patches from
> anyone and he gets the last word wrt to drivers/staging/ (which sort
> of
> contradicts what I said earlier about ownership).
>
> regards,
> dan carpenter
>
prev parent reply other threads:[~2016-10-24 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 5:29 mzoran
2016-10-24 10:54 ` Dan Carpenter
2016-10-24 11:09 ` Michael Zoran
2016-10-24 11:36 ` Dan Carpenter
2016-10-24 11:39 ` Michael Zoran
2016-10-24 11:58 ` Dan Carpenter
2016-10-24 12:12 ` Michael Zoran
2016-10-24 12:30 ` Dan Carpenter
2016-10-24 13:23 ` Greg KH
2016-10-24 13:56 ` Michael Zoran
2016-10-24 14:46 ` Dan Carpenter
2016-10-24 15:13 ` Michael Zoran [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=1477322035.2088.1.camel@crowfest.net \
--to=mzoran@crowfest.net \
--cc=dan.carpenter@oracle.com \
--cc=daniels@collabora.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=popcornmix@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
all inboxes | Powered by JetHome®