From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Dooks <ben-linux@fluff.org>
Cc: magnus.damm@gmail.com, i2c@lm-sensors.org, lethal@linux-sh.org,
linux-sh@vger.kernel.org
Subject: Re: [i2c] [PATCH] i2c: SuperH Mobile I2C Bus Controller V4
Date: Mon, 31 Mar 2008 15:36:08 -0700 [thread overview]
Message-ID: <20080331153608.09293906.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080329175732.GA9638@fluff.org.uk>
On Sat, 29 Mar 2008 17:57:32 +0000
Ben Dooks <ben-linux@fluff.org> wrote:
> On Fri, Mar 28, 2008 at 06:35:30PM +0900, Magnus Damm wrote:
> > This is V4 of the SuperH Mobile I2C Controller Driver. A simple Master
> > only driver for the I2C block included in processors such as sh7343,
> > sh7722 and sh7723. Tested on a sh7722 MigoR using a rs5c732b rtc.
> >
> > Changes since V3:
> > - Added SUPERH Kconfig dependency
> > - Use spin_lock_irqsave() and spin_unlock_irqrestore()
> > - Use IRQF_DISABLED
> > - Checkpatch fixes
> > Changes since V2:
> > - dev_xxx() use
> > - Kill off superfluous ioarea resource
> > - Add SMBus emulation
> > Changes since V1:
> > - Use clk_get()/clk_put()/clk_get_rate() to get peripheral clock rate.
> > - Use pdev->dev.bus_id instead of dev->name
>
> Do we really need these in the change message, we tend to assume that
> the changes before submission aren't really relevant. I would advise
> on removing these.
They are valuable for people who have reviewed earlier versions of the
patchset so yes, please do maintain them.
I will snip them out when I merge them however - this short-term
inter-version information isn't appropriate to the final git commit.
next prev parent reply other threads:[~2008-03-31 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 9:35 [PATCH] i2c: SuperH Mobile I2C Bus Controller V4 Magnus Damm
2008-03-29 17:57 ` [i2c] " Ben Dooks
[not found] ` <20080329175732.GA9638-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-03-29 19:57 ` Jean Delvare
2008-03-31 22:36 ` Andrew Morton [this message]
2008-04-02 1:20 ` [i2c] " Magnus Damm
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=20080331153608.09293906.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ben-linux@fluff.org \
--cc=i2c@lm-sensors.org \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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