mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guillaume Clement <gclement@baobob.org>
To: Forest Bond <forest@alittletooquiet.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] staging: vt6655: fix sparse issues
Date: Tue, 22 Jul 2014 22:08:25 +0200	[thread overview]
Message-ID: <1406059710-30903-1-git-send-email-gclement@baobob.org> (raw)

Those patches fix warnings reported by sparse on the vt6655
driver. This will allow to more easily find real errors with sparse
later if one appears.


Note that checkpatch does return an error for patch 1 and 2 (line over
80 characters) but the line length was not increased by this patch. If
needed, I can do another patch set to fix the 80 column warnings too.

[PATCH 1/5] staging: vt6655: change type of PortOffset to void
[PATCH 2/5] staging: vt6655:fix warning for unexported non-static
[PATCH 3/5] staging: vt6655: statify some variables
[PATCH 4/5] staging: vt6655: remove unused functions
[PATCH 5/5] staging: vt6655: Fix unused function warning

             reply	other threads:[~2014-07-22 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 20:08 Guillaume Clement [this message]
2014-07-22 20:08 ` [PATCH 1/5] staging: vt6655: change type of PortOffset to void __iomem * Guillaume Clement
2014-07-22 22:01   ` Greg Kroah-Hartman
2014-07-22 20:08 ` [PATCH 2/5] staging: vt6655:fix warning for unexported non-static functions Guillaume Clement
2014-07-22 20:08 ` [PATCH 3/5] staging: vt6655: statify some variables Guillaume Clement
2014-07-22 20:08 ` [PATCH 4/5] staging: vt6655: remove unused functions Guillaume Clement
2014-07-22 20:08 ` [PATCH 5/5] staging: vt6655: Fix unused function warning Guillaume Clement

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=1406059710-30903-1-git-send-email-gclement@baobob.org \
    --to=gclement@baobob.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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 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®