From: Jeff Garzik <jeff@garzik.org>
To: Divy Le Ray <divy@chelsio.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
swise@opengridcomputing.com, wenxiong@us.ibm.com
Subject: Re: [PATCH 2/2] cxgb3 - Parity initialization for T3C adapters
Date: Fri, 07 Dec 2007 18:26:39 -0500 [thread overview]
Message-ID: <4759D6AF.5050205@garzik.org> (raw)
In-Reply-To: <4759CD92.2070604@chelsio.com>
Divy Le Ray wrote:
> Jeff Garzik wrote:
>> Divy Le Ray wrote:
>>> From: Divy Le Ray <divy@chelsio.com>
>>>
>>> Add parity initialization for T3C adapters.
>>>
>>> Signed-off-by: Divy Le Ray <divy@chelsio.com>
>>> ---
>>>
>>> drivers/net/cxgb3/adapter.h | 1
>>> drivers/net/cxgb3/cxgb3_main.c | 82 ++++++++++++
>>> drivers/net/cxgb3/cxgb3_offload.c | 15 ++
>>> drivers/net/cxgb3/regs.h | 248
>>> +++++++++++++++++++++++++++++++++++++
>>> drivers/net/cxgb3/sge.c | 24 +++-
>>> drivers/net/cxgb3/t3_hw.c | 131 +++++++++++++++++---
>>> 6 files changed, 472 insertions(+), 29 deletions(-)
>>
>> dropped patches 2-3, did not apply
>>
>>
>
> Hi Jeff,
>
> I noticed that you applied the first one of this 3 patches series to the
> #upstream-fixes branch.
> These patches are intended to the #upstream (2.6.25) branch, as they are
> built on top of the
> last 10 patches committed - 9 from me, and the white space clean up
> (thanks!).
> May be this is the reason why they did not apply.
Ah... you need to tell me these things. I looked for a kernel version
in your messages but did not see one.
Does the patch #1 need to be reverted for 2.6.24?
> On this topic, I have a question: how do I get to see all the netdev-2.6
> branches ?
> After cloning a free netdev-2.6 tree, 'git branch' shows only the
> master branch:
>
> bash-3.1$ git --version
> git version 1.5.3.rc4.29.g74276-dirty
> -bash-3.1$ stg clone
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
> netdev-2.6-fresh
> Cloning
> "git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git"
> into "netdev-2.6-fresh"...
> Initialized empty Git repository in /opt/sources/netdev-2.6-fresh/.git/
> remote: Generating pack...
> remote: Counting objects: 620879
> Done counting 633562 objects.
> remote: Deltifying 633562 objects...
> remote: 100% (633562/633562) done
> Indexing 633562 objects...
> remote: Total 633562 (delta 517968), reused 594305 (delta 478716)
> 100% (633562/633562) done
> Resolving 517968 deltas...
> 100% (517968/517968) done
> Checking 23058 files out...
> 100% (23058/23058) done
> done
> -bash-3.1$ cd netdev-2.6-fresh/
> -bash-3.1$ git branch
> * master
git fetch -f $NETDEV_URL upstream:upstream
copies the latest upstream branch from netdev-2.6.git, and stores it as
your local upstream branch.
You may do the same for #upstream-fixes too.
Jeff
next prev parent reply other threads:[~2007-12-07 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 18:15 [PATCH 2/2] cxgb3 - Parity initialization for T3C adapters Divy Le Ray
2007-12-07 20:02 ` Jeff Garzik
2007-12-07 22:47 ` Divy Le Ray
2007-12-07 23:26 ` Jeff Garzik [this message]
2007-12-08 0:14 ` Divy Le Ray
2007-12-14 23:05 ` Divy Le Ray
2007-12-11 22:27 ` Junio C Hamano
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=4759D6AF.5050205@garzik.org \
--to=jeff@garzik.org \
--cc=divy@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.com \
--cc=wenxiong@us.ibm.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).