From: Jean Delvare <khali@linux-fr.org>
To: "Felipe Balbi" <felipebalbi@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, david-b@pacbell.net,
tony@atomide.com, "Linux I2C" <i2c@lm-sensors.org>
Subject: Re: [PATCH 2/2] I2C: ISP1301_OMAP: New-style i2c driver updates, part 2
Date: Tue, 22 Jan 2008 18:56:15 +0100 [thread overview]
Message-ID: <20080122185615.4a8ebbea@hyperion.delvare> (raw)
In-Reply-To: <31e679430801220413j763589b0j171873c9a90a3cb3@mail.gmail.com>
On Tue, 22 Jan 2008 14:13:58 +0200, Felipe Balbi wrote:
> On Jan 22, 2008 2:01 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > On Thu, 3 Jan 2008 11:59:57 -0500, Felipe Balbi wrote:
> > > - if (machine_is_omap_h2())
> > > - omap_free_gpio(2);
> > > -
> >
> > Why?
>
> Board specific code should go to board files. I'll try to find a
> better way of doing this. Maybe using a private_data.
> Ditto to all cases below.
I agree that board code should ideally not be there, however you can't
just drop it and hope nobody will notice. It needs to be done in such a
way that everything still works afterwards. IMHO it is better move such
changes to a later patch so as to not make this one needlessly complex.
> > (Did you test you patch on OMAP H2?)
>
> Can't remember anymore, but before applying these patches isp1301 was
> crashing the kernel on H2 and H3.
That's bad, this should be fixed, if possible even before applying your
patches.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2008-01-22 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 16:59 [PATCH 0/2] ISP1301 updates Felipe Balbi
2008-01-03 16:59 ` [PATCH 1/2] I2C: ISP1301_OMAP: New-style i2c driver updates, part 1 Felipe Balbi
2008-01-03 16:59 ` [PATCH 2/2] I2C: ISP1301_OMAP: New-style i2c driver updates, part 2 Felipe Balbi
2008-01-22 12:01 ` Jean Delvare
2008-01-22 12:13 ` Felipe Balbi
2008-01-22 17:56 ` Jean Delvare [this message]
2008-01-21 17:15 ` [PATCH 1/2] I2C: ISP1301_OMAP: New-style i2c driver updates, part 1 Jean Delvare
2008-01-21 18:37 ` Felipe Balbi
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=20080122185615.4a8ebbea@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=david-b@pacbell.net \
--cc=felipebalbi@users.sourceforge.net \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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