From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] scc_pata: kill unused variables
Date: Thu, 16 Oct 2008 21:40:56 +0200 [thread overview]
Message-ID: <200810162140.56921.bzolnier@gmail.com> (raw)
In-Reply-To: <200810162305.31300.sshtylyov@ru.mvista.com>
On Thursday 16 October 2008, Sergei Shtylyov wrote:
> Fix the "unused variable" warning in init_hwif_scc() caused by the commit
> 48c3c1072651922ed153bcf0a33ea82cf20df390 (ide: add struct ide_host (take 3)).
> Moreover, remove the write-only variable 'dma_status_port' in init_setup_scc()
> about which gcc gives no warning and which has been there from the very start...
>
> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
applied
prev parent reply other threads:[~2008-10-16 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 19:05 [PATCH] scc_pata: kill unused variables Sergei Shtylyov
2008-10-16 19:40 ` Bartlomiej Zolnierkiewicz [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=200810162140.56921.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).