From: Roland Dreier <rdreier@cisco.com>
To: "Amit S. Kale" <amitkale@linsyssoft.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org, sanjeev@unminc.com,
unmproj@linsyssoft.com
Subject: Re: [PATCH 0/9] Resending NetXen 1G/10G NIC driver patch
Date: Fri, 26 May 2006 13:02:43 -0700 [thread overview]
Message-ID: <ada7j48h7vg.fsf@cisco.com> (raw)
In-Reply-To: <200605261116.50176.amitkale@linsyssoft.com> (Amit S. Kale's message of "Fri, 26 May 2006 11:16:49 +0530")
Amit> We'll implement the minor changes rightaway and post an
Amit> update. We are also thinking about what's the best way to
Amit> incorporate the data structure changes you have
Amit> suggested. Will post a reply on that too soon.
By the way, my suggestion to the original posting still stands: use a
descriptive subject line and include a changelog entry for each patch
that you expect to be merged.
- R.
next prev parent reply other threads:[~2006-05-26 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 10:45 [PATCH 0/9] Resending NetXen 1G/10G NIC driver patch Linsys Contractor Amit S. Kale
2006-05-26 5:46 ` Amit S. Kale
2006-05-26 20:02 ` Roland Dreier [this message]
2006-05-27 11:11 ` Amit S. Kale
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=ada7j48h7vg.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=amitkale@linsyssoft.com \
--cc=netdev@vger.kernel.org \
--cc=sanjeev@unminc.com \
--cc=shemminger@osdl.org \
--cc=unmproj@linsyssoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.