From: Patrick McHardy <kaber@trash.net>
To: Pavel Emelianov <xemul@sw.ru>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
Kirill Korotaev <dev@sw.ru>,
devel@openvz.org
Subject: Re: [PATCH] Rework dev_base via list_head (v2)
Date: Thu, 03 May 2007 16:52:23 +0200 [thread overview]
Message-ID: <4639F727.8080100@trash.net> (raw)
In-Reply-To: <4639F542.7010800@sw.ru>
Pavel Emelianov wrote:
> Patrick McHardy wrote:
>
>>This seems to be missing fs/afs/netdevices.c.
>>
>
>
> Hm... I've cloned the git repo this morning but there's not such file...
>
> $ ls fs/afs/netdevices.c
> /bin/ls: fs/afs/netdevices.c: No such file or directory
>
> Repo was cloned from
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
You need to update, its there in the current tree.
prev parent reply other threads:[~2007-05-03 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 11:36 [PATCH] Rework dev_base via list_head (v2) Pavel Emelianov
2007-05-03 11:44 ` Patrick McHardy
2007-05-03 14:44 ` Pavel Emelianov
2007-05-03 14:52 ` Patrick McHardy [this message]
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=4639F727.8080100@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=dev@sw.ru \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@sw.ru \
/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).