All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Haupt <andre@bitwigglers.org>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, Andre Haupt <andre@bitwigglers.org>
Subject: [PATCH 0/2] parport sparse fixes
Date: Fri, 20 Jun 2008 12:51:43 +0000	[thread overview]
Message-ID: <cover.1213965527.git.andre@bitwigglers.org> (raw)

The following patches fix some warnings sparse gave me, when running
over drivers/parport.

Andre Haupt (2):
  parport: remove superfluous local variable.
  parport: make parport_cs_release static.

 drivers/parport/ieee1284.c   |    2 --
 drivers/parport/parport_cs.c |    2 +-
 2 files changed, 1 insertions(+), 3 deletions(-)


WARNING: multiple messages have this Message-ID (diff)
From: Andre Haupt <andre@bitwigglers.org>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, Andre Haupt <andre@bitwigglers.org>
Subject: [PATCH 0/2] parport sparse fixes
Date: Fri, 20 Jun 2008 14:51:43 +0200	[thread overview]
Message-ID: <cover.1213965527.git.andre@bitwigglers.org> (raw)

The following patches fix some warnings sparse gave me, when running
over drivers/parport.

Andre Haupt (2):
  parport: remove superfluous local variable.
  parport: make parport_cs_release static.

 drivers/parport/ieee1284.c   |    2 --
 drivers/parport/parport_cs.c |    2 +-
 2 files changed, 1 insertions(+), 3 deletions(-)


             reply	other threads:[~2008-06-20 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 12:51 Andre Haupt [this message]
2008-06-20 12:51 ` [PATCH 0/2] parport sparse fixes Andre Haupt
2008-06-20 12:51 ` [PATCH 1/2] parport: remove superfluous local variable Andre Haupt
2008-06-20 12:51   ` Andre Haupt
2008-06-20 12:51   ` [PATCH 2/2] parport: make parport_cs_release static Andre Haupt
2008-06-20 12:51     ` Andre Haupt

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=cover.1213965527.git.andre@bitwigglers.org \
    --to=andre@bitwigglers.org \
    --cc=kernel-janitors@vger.kernel.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 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.