From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: broonie@opensource.wolfsonmicro.com, swarren@wwwdotorg.org,
devicetree-discuss@lists.ozlabs.org, n.voss@weinmann.de,
nicolas.ferre@atmel.com, w.sang@pengutronix.de,
linux-i2c@vger.kernel.org, khali@linux-fr.org,
manabian@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] i2c: change id to let i2c-at91 work
Date: Tue, 16 Oct 2012 10:39:54 +0200 [thread overview]
Message-ID: <20121016083954.GB12801@game.jcrosoft.org> (raw)
In-Reply-To: <507CD0CA.9010006@atmel.com>
On 11:13 Tue 16 Oct , Bo Shen wrote:
> Hi J,
>
> On 10/15/2012 23:02, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >On 17:30 Mon 15 Oct , Bo Shen wrote:
> >>The i2c core driver will turn the platform device ID to busnum
> >>When using platfrom device ID as -1, it means dynamically assigned
> >>the busnum. When writing code, we need to make sure the busnum,
> >>and call i2c_register_board_info(int busnum, ...) to register device
> >>if using -1, we do not know the value of busnum
> >>
> >>In order to solve this issue, set the platform device ID as a fix number
> >>Here using 0 to match the busnum used in i2c_regsiter_board_info()
> >>
> >>Signed-off-by: Bo Shen <voice.shen@atmel.com>
> >>---
> >
> >can you check when this append for the first time to schedule a patch for stable too
>
> OK. I will resend it and add linux stable into the cc list.
no this not how it work
I ask you to check which patch add the regression and then when this is
applied in the kernel we will request greg to apply it too to the stable
But before do that you MUST foudn the commit responsible
Best Regards,
J.
next prev parent reply other threads:[~2012-10-16 8:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 9:30 [PATCH v3 0/2] i2c: change id to let i2c-gpio work Bo Shen
[not found] ` <1350293428-24551-1-git-send-email-voice.shen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2012-10-15 9:30 ` [PATCH v3 1/2] " Bo Shen
2012-10-15 9:30 ` [PATCH v3 2/2] i2c: change id to let i2c-at91 work Bo Shen
[not found] ` <1350293428-24551-3-git-send-email-voice.shen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2012-10-15 15:02 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20121015150244.GZ12801-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-10-16 3:13 ` Bo Shen
2012-10-16 8:39 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
[not found] ` <20121016083954.GB12801-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-10-16 10:25 ` Bo Shen
[not found] ` <507D361C.6020403-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2012-10-16 11:10 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20121016111027.GE12801-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-10-17 2:19 ` Bo Shen
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=20121016083954.GB12801@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=n.voss@weinmann.de \
--cc=nicolas.ferre@atmel.com \
--cc=swarren@wwwdotorg.org \
--cc=voice.shen@atmel.com \
--cc=w.sang@pengutronix.de \
/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).