From: David Miller <davem@davemloft.net>
To: ivecera@redhat.com
Cc: netdev@vger.kernel.org, rasesh.mody@qlogic.com
Subject: Re: [PATCH net-next 0/3] bna: clean-up 2
Date: Sun, 21 Jun 2015 10:32:32 -0700 (PDT) [thread overview]
Message-ID: <20150621.103232.479633005247070982.davem@davemloft.net> (raw)
In-Reply-To: <1434559318-31070-1-git-send-email-ivecera@redhat.com>
From: Ivan Vecera <ivecera@redhat.com>
Date: Wed, 17 Jun 2015 18:41:55 +0200
> Next round of cleaning patches.
Series applied, thanks Ivan.
prev parent reply other threads:[~2015-06-21 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 16:41 [PATCH net-next 0/3] bna: clean-up 2 Ivan Vecera
2015-06-17 16:41 ` [PATCH net-next 1/3] bna: remove unnecessary cast of BIT value Ivan Vecera
2015-06-17 16:41 ` [PATCH net-next 2/3] bna: make pointers to read-only inputs const Ivan Vecera
2015-06-17 16:41 ` [PATCH net-next 3/3] bna: remove superfluous parentheses Ivan Vecera
2015-06-21 17:32 ` 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=20150621.103232.479633005247070982.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ivecera@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rasesh.mody@qlogic.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).