From: Greg KH <greg@kroah.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Recent I2C "dead code removal" breaks pmac sound.
Date: Thu, 11 Nov 2004 10:22:29 -0800 [thread overview]
Message-ID: <20041111182228.GA23236@kroah.com> (raw)
In-Reply-To: <20041111180902.GA8697@iram.es>
On Thu, Nov 11, 2004 at 07:09:02PM +0100, Gabriel Paubert wrote:
> Hi,
>
> a recent patch to drivers/i2c/i2c-core.c removed a bunch of
> functions because they were unused; i2c_smbus_write_block_data
> was in the lot. I happen to have a different definition of dead
> code since grepping for it reveals (in sound/ppc/pmac.h):
>
> #define snd_pmac_keywest_write(i2c,cmd,len,data) i2c_smbus_write_block_data((i2c)->client, cmd, len, data)
>
> I only get a link time error since the removed functions are still
> declared in include/linux/i2c.h, and that is certainly wrong.
>
> For now I have successfully compiled with the following patch
> which ressuscitates the function I need. In a recent pull, the
> offending cset is 1.2114.2.8 from November 5th by arjan.
>
> This patch is _not_ final, but I don't know what sould be done:
> excluding the cset, or applying the following and making
> the include file match the existing functions, or something
> completely different?
Put the function back, and change the pmac.h file to delete the #define,
and replace the snd_pmac_keywest_write function with a real call to
i2c_smbus_write_block_data so things like this don't happen again.
Care to write a patch to do this?
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-11 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 18:09 Recent I2C "dead code removal" breaks pmac sound Gabriel Paubert
2004-11-11 18:22 ` Greg KH [this message]
2004-11-12 12:22 ` Gabriel Paubert
2004-11-12 21:20 ` 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=20041111182228.GA23236@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.