From: Wolfram Sang <wsa@the-dreams.de>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: James Ralston <james.d.ralston@intel.com>,
Seth Heasley <seth.heasley@intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] i2c-ismt: add Initialize DMA buffer code ismt_access()
Date: Sat, 28 Sep 2013 15:10:04 +0200 [thread overview]
Message-ID: <20130928131004.GA3049@katana> (raw)
In-Reply-To: <20130926144115.GB12301@hmsreliant.think-freely.org>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On Thu, Sep 26, 2013 at 10:41:15AM -0400, Neil Horman wrote:
> On Thu, Sep 26, 2013 at 10:40:32AM +0200, Wolfram Sang wrote:
> > On Tue, Sep 24, 2013 at 04:47:55PM -0700, James Ralston wrote:
> > > This patch adds code to Initialize the DMA buffer to compensate for possible hardware data corruption.
> >
> > Take care of the line width here.
> >
> > > Signed-off-by: James Ralston <james.d.ralston@intel.com>
> > > ---
> > > drivers/i2c/busses/i2c-ismt.c | 3 +++
> > > 1 files changed, 3 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/drivers/i2c/busses/i2c-ismt.c b/drivers/i2c/busses/i2c-ismt.c
> > > index 8ed79a0..d3f30ea 100644
> > > --- a/drivers/i2c/busses/i2c-ismt.c
> > > +++ b/drivers/i2c/busses/i2c-ismt.c
> > > @@ -393,6 +393,9 @@ static int ismt_access(struct i2c_adapter *adap, u16 addr,
> > >
> > > desc = &priv->hw[priv->head];
> > >
> > > + /* Initialize the DMA buffer */
> > > + memset(priv->dma_buffer, 0, (I2C_SMBUS_BLOCK_MAX+1));
> >
> > sizeof()?
> >
> Agreed.
Fixed that myself so it can be in my pull-request to Linus today.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-09-28 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 23:47 [PATCH 1/1] i2c-ismt: add Initialize DMA buffer code ismt_access() James Ralston
2013-09-26 8:40 ` Wolfram Sang
2013-09-26 14:41 ` Neil Horman
2013-09-28 13:10 ` Wolfram Sang [this message]
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=20130928131004.GA3049@katana \
--to=wsa@the-dreams.de \
--cc=james.d.ralston@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=seth.heasley@intel.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