linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>,
	linux-can@vger.kernel.org
Cc: Jean Delvare <jdelvare@suse.com>
Subject: Re: Request for proper hardware dependencies
Date: Tue, 13 May 2014 16:37:20 +0200	[thread overview]
Message-ID: <53722E20.9080405@pengutronix.de> (raw)
In-Reply-To: <21352.42929.159377.243822@gargle.gargle.HOWL>

[-- Attachment #1: Type: text/plain, Size: 2186 bytes --]

On 05/06/2014 11:13 AM, Uwe Bonnes wrote:
> Hallo,
> 
> the number of kernel driver exploded in the last years and so the kernel
> configuration. Distribution mantainers must at some point limit compiled
> driver at least partly to the driver needed one on a given arch. However the
> distribution maintainers mosty can't always know what they deal about.
> 
> For me this resulted in loosing socketcan from the Opensuse Kernels in
> between 12.3 up to some weeks ago, as one maintainer (not Jean) matched
> socketcan in error with "SPI" which is not related to normal desktop
> machines. See
> http://lists.opensuse.org/archive/opensuse-bugs/2014-01/msg00970.html.
> Opensuse 13.1 recent kernels and the next release will have socketcan again,
> but in the course of the discussion Jean Delvare pointed some weak points in
> socketcan configuration, leading to compilation on driver not needed on some
> archs:
> 
>>>>>> "Jean" == Jean Delvare <jdelvare@suse.com> writes:
> 
>     Jean> For the record, hardware dependencies on CAN device drivers aren't
>     Jean> that bad in general, I've seen worse in several other subsystems.
> 
>     Jean> That being said, there is still some room for improvement. For
>     Jean> example, CAN_AT91 could depend on ARCH_AT91 instead of just ARM,
>     Jean> PCH_CAN could depend on X86, and a few drivers with "ISA" in their
>     Jean> description should probably depend on ISA. I'm also not sure why
>     Jean> CAN_MSCAN alternatively depends on M68K instead of just
>     Jean> ARM. That's just from a quick look from the non-initiate I am,
>     Jean> there may be more dependency fix-ups possible.  I'll send a few
>     Jean> patches out if I can find some time for that today.
> 
> Please consider openly his patches or even better consider a cleanup yourself.

I've applied all 3 patches by Jean to can-next.

Tnx,
Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]

  reply	other threads:[~2014-05-13 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06  9:13 Request for proper hardware dependencies Uwe Bonnes
2014-05-13 14:37 ` Marc Kleine-Budde [this message]
2014-05-13 15:31   ` Jean Delvare

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=53722E20.9080405@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=bon@elektron.ikp.physik.tu-darmstadt.de \
    --cc=jdelvare@suse.com \
    --cc=linux-can@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;
as well as URLs for NNTP newsgroup(s).