All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Greg KH <greg@kroah.com>
Cc: Subbu Seetharaman <subbus@serverengines.com>,
	netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] benet: BladeEngine 10Gb NIC driver
Date: Mon, 03 Nov 2008 15:42:28 -0500	[thread overview]
Message-ID: <490F6234.4060805@garzik.org> (raw)
In-Reply-To: <20081103201930.GB13299@kroah.com>

Greg KH wrote:
> On Mon, Nov 03, 2008 at 02:52:07PM -0500, Jeff Garzik wrote:
>> Greg KH wrote:
>>> On Mon, Nov 03, 2008 at 04:25:12AM -0800, Subbu Seetharaman wrote:
>>>> If we could get more specific feedback about the areas that require
>>>> cleanup, we can take care of them quickly.  
>>>> Since the last posting, we have brought up the driver in a PPC system
>>>> and fixed some endianness issues.  As soon as I have some specific
>>>> feedback, we can update the driver with these fixes as well.
>>>>
>>>> Please let me know as soon as the driver is in the staging area.
>>> Does someone have a pointer to the driver, so that we can see what is
>>> needed to be done?
>> It was in my email :)  Repeating,
>>
>> The 'benet' branch of
>> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
>>
>> It should be suitable for pulling directly into staging.
> 
> Hm, call me extreemly stupid, but I don't see anything in that branch
> for this driver.
> 
> Here's what I did:
>   git fetch git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git benet master:jeff
>   git checkout jeff
> 
> Even looking around at this tree with 'gitk --all' I don't see anything.
> So what did I do wrong here?

Well, the commit has been there long enough to mirror out, and show up 
on the web interface:

http://git.kernel.org/?p=linux/kernel/git/jgarzik/netdev-2.6.git;a=shortlog;h=benet

therefore I am guessing there is some git user error here... but I could 
not say what, since I am unfamiliar with your style of git invocation.

I would recommend creating a new branch, or switching to an existing 
one, and then pulling into it.  Pulling from a branch always works in my 
experience, and that's what I've been doing since git was first written.

URL=git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
git checkout -b tmp master
git pull $URL benet

Regards,

	Jeff




  reply	other threads:[~2008-11-03 20:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 12:25 [RESEND] benet: BladeEngine 10Gb NIC driver Subbu Seetharaman
2008-11-03 19:36 ` Greg KH
2008-11-03 19:52   ` Jeff Garzik
2008-11-03 19:55     ` Greg KH
2008-11-03 20:19     ` Greg KH
2008-11-03 20:42       ` Jeff Garzik [this message]
2008-11-03 20:46         ` Greg KH
2008-11-03 20:55           ` Jeff Garzik
2008-11-03 21:40             ` Greg KH
2008-11-04 10:41       ` Ilpo Järvinen
2008-11-05  5:02         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2008-09-16  9:00 Subbu Seetharaman
2008-11-02 13:15 ` Jeff Garzik
2008-11-02 15:37   ` Greg KH

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=490F6234.4060805@garzik.org \
    --to=jeff@garzik.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=subbus@serverengines.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.