From: Steven Newbury <steve@snewbury.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Naren Sankar <nsankar@broadcom.com>,
Jarod Wilson <jarod@wilsonet.com>,
Scott Davilla <davilla@4pi.com>,
Manu Abraham <abraham.manu@gmail.com>
Subject: Re: [PATCH] staging: Merge Crystal HD driver with linuxtv.org
Date: Tue, 29 Oct 2013 14:51:00 +0000 [thread overview]
Message-ID: <1383058260.2598.57.camel@artifact> (raw)
In-Reply-To: <1383051272.2598.55.camel@artifact>
On Tue, 2013-10-29 at 12:54 +0000, Steven Newbury wrote:
> Hi Greg,
> I'm making good progress. My plan is to break/clean up the patch
> logically:
>
> patch1: Clean up debug/error messages DONE - (this has actually
> resulted in some bug fixes)
>
<- patch1b: Clean up typedefs (missed this in my list, but it's what I'm
working on right now) WIP
> patch2: Remove commented out/unused code TODO
>
> patch3: Power management support TODO
>
> patch4: other misc fixes/changes (may be more than one patch) with
> details in log message
>
> patch5: Rename driver to crystalhd (instead of bcm70012) DONE
>
> patch6: Restructure driver to prepare for BCM70015 support by splitting
> out (BCM70012) hw specific parts. DONE
>
> patch7: Add BCM70015 support MOSTLY DONE - some clean up needed
>
>
> To me this makes more sense than trying to apply the patches as applied
> to the linuxtv.org git repo since there's a lot of irrelevant code churn
> and changes in commits which are undocumented in the log message along
> with the fact they won't apply cleanly on top of the existing staging
> driver anyway.
prev parent reply other threads:[~2013-10-29 13:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 16:27 [PATCH] staging: Merge Crystal HD driver with linuxtv.org Steven Newbury
2013-10-27 15:54 ` Greg KH
2013-10-27 17:12 ` Steven Newbury
2013-10-27 16:26 ` Greg KH
2013-10-27 18:15 ` Steven Newbury
2013-10-29 12:54 ` Steven Newbury
2013-10-29 14:51 ` Steven Newbury [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=1383058260.2598.57.camel@artifact \
--to=steve@snewbury.org.uk \
--cc=abraham.manu@gmail.com \
--cc=davilla@4pi.com \
--cc=gregkh@linuxfoundation.org \
--cc=jarod@wilsonet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsankar@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.