linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Re: [PATCH] i2c_intel_mid: Fix slash in sysfs name
Date: Wed, 15 Dec 2010 10:08:15 +0100	[thread overview]
Message-ID: <20101215100815.44fb8b83@endymion.delvare> (raw)
In-Reply-To: <20101214152849.7265.93628.stgit-Z/y2cZnRghHXmaaqVzeoHQ@public.gmane.org>

Hi Alan,

On Tue, 14 Dec 2010 15:29:08 +0000, Alan Cox wrote:
> From: Alan Cox <alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
> 
> This gets caught by the new sanity check code.

New sanity check of what? Where's the code?

> Instead of the slash use a
> different symbol. This was originally found by Major Lee who proposed a
> rather more complex patch which changed the name according to the chip
> type.
> 
> On the basis that we are in a late -rc and making Linus grumpy isn't always
> a good idea (however fun) this is a simple alternative.
> 
> Signed-off-by: Alan Cox <alan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
> ---
> 
>  drivers/i2c/busses/i2c-intel-mid.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> 
> diff --git a/drivers/i2c/busses/i2c-intel-mid.c b/drivers/i2c/busses/i2c-intel-mid.c
> index 657f314..da4bbdd 100644
> --- a/drivers/i2c/busses/i2c-intel-mid.c
> +++ b/drivers/i2c/busses/i2c-intel-mid.c
> @@ -1035,7 +1035,7 @@ static int __devinit intel_mid_i2c_probe(struct pci_dev *dev,
>  
>  	/* Initialize struct members */
>  	snprintf(mrst->adap.name, sizeof(mrst->adap.name),
> -		"MRST/Medfield I2C at %lx", start);
> +		"Intel MID I2C at %lx", start);
>  	mrst->adap.owner = THIS_MODULE;
>  	mrst->adap.algo = &intel_mid_i2c_algorithm;
>  	mrst->adap.dev.parent = &dev->dev;

Having a slash in an I2C adapter name shouldn't be a problem. The real
problem is below:

	err = request_irq(dev->irq, intel_mid_i2c_isr, IRQF_SHARED,
					mrst->adap.name, mrst);

Using the adapter name to request the IRQ is silly. The very same issue
was fixed in i2c-pca-platform recently:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=323584436db0cb05286425d4dfd9516fce88487f

You want to use a short name for the interrupt. Either the driver name,
or if you really want something device-specific, the bus device name.

-- 
Jean Delvare

  parent reply	other threads:[~2010-12-15  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 15:29 [PATCH] i2c_intel_mid: Fix slash in sysfs name Alan Cox
     [not found] ` <20101214152849.7265.93628.stgit-Z/y2cZnRghHXmaaqVzeoHQ@public.gmane.org>
2010-12-15  9:08   ` Jean Delvare [this message]
     [not found]     ` <20101215100815.44fb8b83-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-04  0:55       ` Ben Dooks
     [not found]         ` <4D227005.3010000-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
2011-01-04 10:32           ` Alan Cox

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=20101215100815.44fb8b83@endymion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).