From: Prarit Bhargava <prarit@redhat.com>
To: Jack Morgenstein <jackm@dev.mellanox.co.il>
Cc: netdev@vger.kernel.org, dledford@redhat.com, amirv@mellanox.com,
davem@davemloft.net, ogerlitz@mellanox.com
Subject: Re: [PATCH 2/2] net, mellanox mlx4 Fix compile warnings [v4]
Date: Tue, 01 Oct 2013 11:25:28 -0400 [thread overview]
Message-ID: <524AE968.608@redhat.com> (raw)
In-Reply-To: <20131001181742.72e603d1@jpm-OptiPlex-GX620>
On 10/01/2013 11:17 AM, Jack Morgenstein wrote:
> Since we are in the middle of submitting patches which touch the file
> "resource_tracker.c", I would really like to hold off on these warning
> fixes for a bit, and I'll handle the changes for all the functions at
> once to conform (correctly!) to the format suggested by Dave Miller.
>
> -Jack
Hey Jack, np. Thanks for looking.
P.
next prev parent reply other threads:[~2013-10-01 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 13:24 [PATCH 1/2] net, vxlan Fix compile warning [v4] Prarit Bhargava
2013-10-01 13:24 ` [PATCH 2/2] net, mellanox mlx4 Fix compile warnings [v4] Prarit Bhargava
2013-10-01 15:17 ` Jack Morgenstein
2013-10-01 15:25 ` Prarit Bhargava [this message]
2013-10-01 16:57 ` David Miller
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=524AE968.608@redhat.com \
--to=prarit@redhat.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=jackm@dev.mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.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).