netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hannes@hanneseder.net
Cc: netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] drivers/isdn: fix sparse warnings
Date: Fri, 27 Feb 2009 01:01:29 -0800 (PST)	[thread overview]
Message-ID: <20090227.010129.221180189.davem@davemloft.net> (raw)
In-Reply-To: <20090225230737.5377.31370.stgit@localhost.localdomain>

From: Hannes Eder <hannes@hanneseder.net>
Date: Thu, 26 Feb 2009 00:08:20 +0100

> The following series fixes some sparse warnings in drivers/isdn.
> 
> ---
> 
> Hannes Eder (5):
>       drivers/isdn/hardware/eicon: fix sparse warnings: Should it be static?
>       drivers/isdn/hardware/icon: fix sparse warning: cast truncates bits
>       drivers/isdn/hisax: fix sparse warning: Should it be static?
>       drivers/isdn/act2000: fix sparse warning: symbol shadows an earlier one
>       drivers/isdn/capi: fix sparse warning: context imbalance

Applied to net-next-2.6, thanks!

      parent reply	other threads:[~2009-02-27  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 23:08 [PATCH 0/5] drivers/isdn: fix sparse warnings Hannes Eder
2009-02-25 23:08 ` [PATCH 1/5] drivers/isdn/capi: fix sparse warning: context imbalance Hannes Eder
2009-02-25 23:09 ` [PATCH 2/5] drivers/isdn/act2000: fix sparse warning: symbol shadows an earlier one Hannes Eder
2009-02-25 23:11 ` [PATCH 3/5] drivers/isdn/hisax: fix sparse warning: Should it be static? Hannes Eder
2009-02-25 23:11 ` [PATCH 4/5] drivers/isdn/hardware/icon: fix sparse warning: cast truncates bits Hannes Eder
2009-02-25 23:11 ` [PATCH 5/5] drivers/isdn/hardware/eicon: fix sparse warnings: Should it be static? Hannes Eder
2009-02-27  9:01 ` David Miller [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=20090227.010129.221180189.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hannes@hanneseder.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).