From: Laurent Pinchart <laurent.pinchart@skynet.be>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: "Bryan Wu" <cooloney@kernel.org>,
linux-uvc-devel@lists.berlios.de, video4linux-list@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Video/UVC: Fix unaligned exceptions in uvc video driver.
Date: Tue, 11 Nov 2008 18:11:34 +0100 [thread overview]
Message-ID: <200811111811.35098.laurent.pinchart@skynet.be> (raw)
In-Reply-To: <8A42379416420646B9BFAC9682273B6D065BA534@limkexm3.ad.analog.com>
On Monday 10 November 2008, Hennerich, Michael wrote:
> > -----Original Message-----
> > From: Laurent Pinchart [mailto:laurent.pinchart@skynet.be]
> > Sent: Sunday, November 09, 2008 1:55 PM
> > To: Bryan Wu
> > Cc: linux-uvc-devel@lists.berlios.de; video4linux-list@redhat.com;
> > linux-kernel@vger.kernel.org; Michael Hennerich
> > Subject: Re: [PATCH] Video/UVC: Fix unaligned exceptions in uvc video
> > driver.
> >
> > Hi Bryan, Michael,
> >
> > Thanks for the patch.
> >
> > On Thursday 06 November 2008, Bryan Wu wrote:
> > > From: Michael Hennerich <michael.hennerich@analog.com>
> > >
> > > buffer can be odd aligned on some NOMMU machine such as Blackfin
> >
> > The comment is a bit misleading. Buffers can be odd-aligned independently
> > off the machine type. The issue comes from machines that can't access
> > unaligned memory. Something like "Fix access to unaligned memory" would be
> > better.
[snip]
> > What about using get_unaligned_le16 and get_unaligned_le32 directly ?
> > Lines would be shorter and could be kept behind the 80 columns limit more
> > easily.
> > Tell me if you want to resubmit or if I should make the modification
> > myself (including the patch description).
>
> Laurent,
>
> Well - I just used the same style already used in various other places
> in the uvc driver. - Just wanted to be consistent.
No worries. get_unaligned_le{16|32} has been introduced in the kernel recently
and I haven't updated the uvcvideo driver like I should have. I'll fix that.
> If you don't mind doing the changes (including the patch description),
> please go ahead.
Ok I'll fix and submit the patch.
Best regards,
Laurent Pinchart
prev parent reply other threads:[~2008-11-11 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 9:17 Bryan Wu
2008-11-09 12:55 ` Laurent Pinchart
2008-11-10 2:07 ` Bryan Wu
2008-11-10 10:51 ` Hennerich, Michael
2008-11-11 17:11 ` Laurent Pinchart [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=200811111811.35098.laurent.pinchart@skynet.be \
--to=laurent.pinchart@skynet.be \
--cc=Michael.Hennerich@analog.com \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-uvc-devel@lists.berlios.de \
--cc=video4linux-list@redhat.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
all inboxes | Powered by JetHome®