From: Divy Le Ray <divy@chelsio.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Steve Wise <swise@opengridcomputing.com>,
wenxiong@us.ibm.com
Subject: Re: [PATCH 2/2] cxgb3 - Parity initialization for T3C adapters
Date: Fri, 07 Dec 2007 16:14:56 -0800 [thread overview]
Message-ID: <4759E200.3050607@chelsio.com> (raw)
In-Reply-To: <4759D6AF.5050205@garzik.org>
Jeff Garzik wrote:
>
> 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.
>
I had put it in the introduction mail, I should have added the kernel
version in the patch titles.
I'll do from now on.
>
> Does the patch #1 need to be reverted for 2.6.24?
>
No, it can be applied to 2.6.24.
The 2 next patches seem to apply cleanly on #upstream when patch #1 is
popped out the patch stack.
>
> > On this topic, I have a question: how do I get to see all the netdev-2.6
> > branches ?
>
>
> 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.
>
That made it.
Thanks a lot!
Cheers,
Divy
next prev parent reply other threads:[~2007-12-08 0:15 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
2007-12-08 0:14 ` Divy Le Ray [this message]
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=4759E200.3050607@chelsio.com \
--to=divy@chelsio.com \
--cc=jeff@garzik.org \
--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).