netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mithlesh Thukral <mithlesh@netxen.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, amitkale@netxen.com,
	netxenproj@linsyssoft.com, rob@netxen.com
Subject: Re: [PATCH 2/2] NetXen: Updates for register access routines
Date: Fri, 18 May 2007 17:00:45 +0530	[thread overview]
Message-ID: <200705181700.45421.mithlesh@netxen.com> (raw)
In-Reply-To: <464CF7A0.2090604@garzik.org>

On Friday 18 May 2007 06:17, Jeff Garzik wrote:
> Mithlesh Thukral wrote:
> > NetXen: Changes related to registers and their access routines
> > This patch updates the various access routines to access different
> > control and status settings present in different register locations.
> > This will fix problems related to working of different ports in
> > multi Port card.
> >
> > Signed-off by: Milan Bag <mbag@netxen.com>
> > Signed-off by: Adhiraj Joshi <adhiraj@netxen.com>
> > Acked-by: Mithlesh Thukral <mithlesh@netxen.com>
> > ---
> >  drivers/net/netxen/netxen_nic.h      |   96 ++++++++++---------------
> >  drivers/net/netxen/netxen_nic_hw.h   |   65 +++-------------
> >  drivers/net/netxen/netxen_nic_init.c |   17 ++--
> >  3 files changed, 65 insertions(+), 113 deletions(-)
>
> not applied.  This patch removes a bunch of endianness changes.
Ok. I will take care of these changes in the next patchset that i submit.
Thanks for applying the first patch.

--
Mithlesh Thukral

  reply	other threads:[~2007-05-18 11:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 13:53 [PATCH 2/2] NetXen: Updates for register access routines Mithlesh Thukral
2007-05-18  0:47 ` Jeff Garzik
2007-05-18 11:30   ` Mithlesh Thukral [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-04 16:11 Mithlesh Thukral
2007-05-02 15:18 Mithlesh Thukral
2007-05-02 20:31 ` Francois Romieu

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=200705181700.45421.mithlesh@netxen.com \
    --to=mithlesh@netxen.com \
    --cc=amitkale@netxen.com \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=netxenproj@linsyssoft.com \
    --cc=rob@netxen.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).