mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manu Abraham <abraham.manu@gmail.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Greg KH <greg@kroah.com>, Peter Paul <abnominales@web.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch staging] BCM70010 (crystalhd) Linux Driver
Date: Sun, 3 Jan 2010 03:14:35 +0400	[thread overview]
Message-ID: <1a297b361001021514h19f814d7w586fd0dbb66d98fa@mail.gmail.com> (raw)
In-Reply-To: <9e4733911001021403n7ba076d0na423ae50e2983171@mail.gmail.com>

On Sun, Jan 3, 2010 at 2:03 AM, Jon Smirl <jonsmirl@gmail.com> wrote:
> On Sat, Jan 2, 2010 at 1:17 PM, Manu Abraham <abraham.manu@gmail.com> wrote:
>> Hi Greg,
>>
>> On Sat, Jan 2, 2010 at 8:34 PM, Greg KH <greg@kroah.com> wrote:
>>> On Sat, Jan 02, 2010 at 08:05:38PM +0400, Manu Abraham wrote:
>>>> Hi Greg,
>>>>
>>>> > I'm glad to do so if someone wants to help work on it there and shephard
>>>> > it into the main kernel tree.
>>>>
>>>> Please find the initial round of cleaned up patches for staging,
>>>> applied against linux-next.
>>>
>>> Did you really author this driver?  If so, that's fine, just checking.
>>> If not, please put the correct authorship "From:" in the patch.
>>
>> I am not the author of the driver. I just picked it up and cleaned it
>> up for Coding style changes for it to be included.
>
> I'm not against this submission, but would it be better to wait until
> Monday when the Broadcom authors are back as see if they want to
> submit their own driver? That way changes would end up back in their
> internal VCS.


Sure, of course,


> I'd like to see a real datasheet for this chip, the public one is
> nothing but a marketing blurb.

You mean a user manual with a description of the registers, don't you ?
Decoder datasheets from whichever manufacturer rarely come into
public. Even with NDA's it is quite hard to get hold of a "proper one"

Regards,
Manu

  reply	other threads:[~2010-01-02 23:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 20:06 Peter Paul
2009-12-31 13:18 ` Andrey Panin
2010-01-01  0:19   ` Greg KH
     [not found]     ` <1a297b361001020805y6b00af83g81cf8492aa73bc3b@mail.gmail.com>
2010-01-02 16:34       ` [patch staging] " Greg KH
2010-01-02 18:17         ` Manu Abraham
2010-01-02 19:21           ` Greg KH
2010-01-02 20:08             ` Manu Abraham
2010-01-02 22:03           ` Jon Smirl
2010-01-02 23:14             ` Manu Abraham [this message]
2010-01-03  4:51             ` Jarod Wilson
2010-01-03 17:34               ` 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=1a297b361001021514h19f814d7w586fd0dbb66d98fa@mail.gmail.com \
    --to=abraham.manu@gmail.com \
    --cc=abnominales@web.de \
    --cc=greg@kroah.com \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®