From: David Miller <davem@davemloft.net>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, Sandeep.Kumar@freescale.com,
afleming@freescale.com, netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] gianfar: Fix compiler and sparse warnings
Date: Sun, 08 Nov 2009 00:44:00 -0800 (PST) [thread overview]
Message-ID: <20091108.004400.154757092.davem@davemloft.net> (raw)
In-Reply-To: <20091104225300.GC29537@oksana.dev.rtsoft.ru>
From: Anton Vorontsov <avorontsov@ru.mvista.com>
Date: Thu, 5 Nov 2009 01:53:00 +0300
> commit fba4ed030cfae7efdb6b79a57b0c5a9d72c9de83 ("gianfar: Add Multiple
> Queue Support") introduced the following warnings:
...
> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Applied.
prev parent reply other threads:[~2009-11-08 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 22:53 [PATCH 3/3] gianfar: Fix compiler and sparse warnings Anton Vorontsov
2009-11-08 8:44 ` 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=20091108.004400.154757092.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Sandeep.Kumar@freescale.com \
--cc=afleming@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.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).