public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Bernhard Walle <walle@corscience.de>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon: Add Lanai board USB clock type
Date: Tue, 12 Oct 2010 08:54:26 -0700	[thread overview]
Message-ID: <20101012155426.GA15238@kroah.com> (raw)
In-Reply-To: <4CB345C1.80709@caviumnetworks.com>

On Mon, Oct 11, 2010 at 10:13:37AM -0700, David Daney wrote:
> On 10/11/2010 10:05 AM, Bernhard Walle wrote:
>> Am 11.10.2010 18:53, schrieb David Daney:
>>> On 10/11/2010 03:09 AM, Bernhard Walle wrote:
>>>> Add the LANAI2 board to __cvmx_helper_board_usb_get_clock_type(). It
>>>> also uses the USB_CLOCK_TYPE_CRYSTAL_12 clock.
>>>>
>>>> Signed-off-by: Bernhard Walle<walle@corscience.de>
>>>> ---
>>>>    drivers/staging/octeon/cvmx-helper-board.c |    1 +
>>>>    1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>>> NAK.
>>>
>>> We don't currently support USB, so churning up this file doesn't help
>>> anything.
>>
>> Well, agreed, but why not removing that code entirely then?
>>
>
> That is the eventual plan.

Why not do that now?

Or add USB support to the driver, but don't leave it in the in-kernel
driver and expect users to know that this is something they shouldn't be
doing.

Also, why aren't you going to support the USB devices?  What's wrong
with that?

thanks,

greg k-h

  reply	other threads:[~2010-10-12 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 10:09 [PATCH] staging: octeon: Add Lanai board USB clock type Bernhard Walle
2010-10-11 16:53 ` David Daney
2010-10-11 17:05   ` Bernhard Walle
2010-10-11 17:13     ` David Daney
2010-10-12 15:54       ` Greg KH [this message]
2010-10-12 16:56         ` David Daney
2010-10-13 16:39           ` Bernhard Walle
2010-10-13 21:02             ` 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=20101012155426.GA15238@kroah.com \
    --to=greg@kroah.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walle@corscience.de \
    /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