From: David Miller <davem@davemloft.net>
To: corbet@lwn.net
Cc: wg@grandegger.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, oliver.hartkopp@volkswagen.de
Subject: Re: [PATCH 4/8] can: Driver for the SJA1000 CAN controller
Date: Fri, 20 Feb 2009 00:46:32 -0800 (PST) [thread overview]
Message-ID: <20090220.004632.226039985.davem@davemloft.net> (raw)
In-Reply-To: <20090219171440.0c8286a1@bike.lwn.net>
From: Jonathan Corbet <corbet@lwn.net>
Date: Thu, 19 Feb 2009 17:14:40 -0700
> I won't be able to look at all of these...
>
> > diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
> > index d609895..78a412b 100644
> > --- a/drivers/net/can/Kconfig
> > +++ b/drivers/net/can/Kconfig
> > @@ -35,6 +35,17 @@ config CAN_CALC_BITTIMING
> > files "tq", "prop_seg", "phase_seg1", "phase_seg2" and "sjw".
> > If unsure, say Y.
> >
> > +config CAN_SJA1000
> > + depends on CAN_DEV
> > + tristate "Philips SJA1000"
> > + ---help---
> > + The SJA1000 is one of the top CAN controllers out there. As it
> > + has a multiplexed interface it fits directly to 8051
> > + microcontrollers or into the PC I/O port space. The SJA1000
> > + is a full CAN controller, with shadow registers for RX and TX.
> > + It can send and receive any kinds of CAN frames (SFF/EFF/RTR)
> > + with a single (simple) filter setup.
>
> This sounds more like advertising text. But what people need to know is
> whether they should enable it or not.
Totally agreed, this Kconfig help text is inappropriate
at best.
next prev parent reply other threads:[~2009-02-20 8:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 19:01 [PATCH 0/8] can: CAN network device driver interface and drivers Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 1/8] can: Documentation for the CAN device driver interface Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 2/8] can: Update MAINTAINERS and CREDITS file Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 3/8] can: CAN Network device driver and SYSFS interface Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 4/8] can: Driver for the SJA1000 CAN controller Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 5/8] can: SJA1000 generic platform bus driver Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 6/8] can: SJA1000 driver for EMS PCI cards Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 7/8] can: SJA1000 driver for Kvaser " Wolfgang Grandegger
2009-02-19 19:01 ` [PATCH 8/8] can: Driver for the Freescale MSCAN controller Wolfgang Grandegger
2009-02-20 0:14 ` [PATCH 4/8] can: Driver for the SJA1000 CAN controller Jonathan Corbet
2009-02-20 8:46 ` David Miller [this message]
2009-02-20 9:35 ` Wolfgang Grandegger
2009-05-01 18:21 ` Wolfgang Grandegger
2009-02-19 23:49 ` [PATCH 3/8] can: CAN Network device driver and SYSFS interface Jonathan Corbet
2009-02-20 8:39 ` Wolfgang Grandegger
2009-02-20 9:44 ` Patrick McHardy
2009-02-21 15:09 ` Wolfgang Grandegger
2009-02-23 9:55 ` Patrick McHardy
2009-02-23 14:57 ` Wolfgang Grandegger
2009-02-24 9:38 ` Patrick McHardy
2009-02-24 16:29 ` Wolfgang Grandegger
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=20090220.004632.226039985.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).