From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, ddutt@Brocade.COM
Subject: Re: [PATCH 1/2] bna: fix for clean fw re-initialization
Date: Mon, 18 Apr 2011 12:28:17 -0700 (PDT) [thread overview]
Message-ID: <20110418.122817.15229388.davem@davemloft.net> (raw)
In-Reply-To: <E5313AF6F2BFD14293E5FD0F94750F86A5D7348A7B@HQ1-EXCH01.corp.brocade.com>
From: Rasesh Mody <rmody@brocade.com>
Date: Mon, 18 Apr 2011 12:26:12 -0700
> We were not able to see these patches when we did a git-pull of
> net-next-2.6. We were wondering if the patches are stuck behind
> others and not committed to the tree.
They went into net-2.6 since they are bug fixes and you didn't specify
which tree you wanted them to appear in.
prev parent reply other threads:[~2011-04-18 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 18:05 [PATCH 1/2] bna: fix for clean fw re-initialization Rasesh Mody
2011-04-14 18:05 ` [PATCH 2/2] bna: fix memory leak during RX path cleanup Rasesh Mody
2011-04-14 20:40 ` David Miller
2011-04-14 20:39 ` [PATCH 1/2] bna: fix for clean fw re-initialization David Miller
2011-04-18 19:26 ` Rasesh Mody
2011-04-18 19:28 ` 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=20110418.122817.15229388.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ddutt@Brocade.COM \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.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).