From: Jean Delvare <khali@linux-fr.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 10/10 v2] Document I2C_MPC option for 86xx too.
Date: Fri, 9 Jun 2006 09:37:37 +0200 [thread overview]
Message-ID: <20060609093737.f66d5a41.khali@linux-fr.org> (raw)
In-Reply-To: <1149804296.23938.298.camel@cashmere.sps.mot.com>
Hi Jon,
Please add a paragraph explaining what the patch does. It will be used
as the git commit message.
> Signed-off-by: Jon Loeliger <jdl@freescale.com>
>
> ---
> drivers/i2c/busses/Kconfig | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index d6d4494..fbeae82 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -252,12 +252,12 @@ config I2C_POWERMAC
> will be called i2c-powermac.
>
> config I2C_MPC
> - tristate "MPC107/824x/85xx/52xx"
> + tristate "MPC107/824x/85xx/52xx/86xx"
Maybe leave 52xx at the end, as it seems to be special?
> depends on I2C && PPC32
> help
> If you say yes to this option, support will be included for the
> built-in I2C interface on the MPC107/Tsi107/MPC8240/MPC8245 and
> - MPC85xx family processors. The driver may also work on 52xx
> + MPC85xx/MPC8641 family processors. The driver may also work on 52xx
> family processors, though interrupts are known not to work.
>
> This driver can also be built as a module. If so, the module
>
This isn't very consistent, you first say 86xx as if several chips were
supported, then only list the MPC8641. Also, "MPC85xx family" made
sense but "MPC8641 family" doesn't.
When fixed, do you expect me to take that patch, or will it be merged
through the powerpc git tree?
--
Jean Delvare
next prev parent reply other threads:[~2006-06-09 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 22:04 [PATCH 10/10 v2] Document I2C_MPC option for 86xx too Jon Loeliger
2006-06-09 7:37 ` Jean Delvare [this message]
2006-06-09 13:50 ` Jon Loeliger
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=20060609093737.f66d5a41.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.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 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.