From: David Miller <davem@davemloft.net>
To: Sreenivasa.Honnur@neterion.com
Cc: netdev@vger.kernel.org, support@neterion.com
Subject: Re: [net-next-2.6 PATCH 1/9] vxge: Modify __vxge_hw_device_is_privilaged() to not assume function-0 as privilaged function.
Date: Mon, 05 Oct 2009 02:20:17 -0700 (PDT) [thread overview]
Message-ID: <20091005.022017.252887922.davem@davemloft.net> (raw)
In-Reply-To: <Pine.GSO.4.10.10910050503530.2346-100000@guinness>
From: Sreenivasa Honnur <Sreenivasa.Honnur@neterion.com>
Date: Mon, 5 Oct 2009 05:06:06 -0400 (EDT)
> - vxge driver was assuming function-0 is always the privilaged function. Now that
> restriction has been removed any function can act as a privilaged function.
>
> - This patch modifies the __vxge_hw_device_is_privilaged routine to not assume
> function-0 as the privileged function.
>
> Signed-off-by: Sreenivasa Honnur <sreenivasa.honnur@neterion.com>
> ---
> diff -urpN orig//drivers/net/vxge/vxge-config.c patch1//drivers/net/vxge/vxge-config.c
> --- orig//drivers/net/vxge/vxge-config.c 2009-09-03 22:39:48.000000000 -0700
> +++ patch1//drivers/net/vxge/vxge-config.c 2009-09-03 23:11:24.000000000 -0700
You can't have the double slash there in your paths, this
gets interpreted as "/drivers/net/vxge/vxge-config.c" by
all the patch applying tools.
Please "-p1" root your patches properly as described in
linux/Documentation/SubmittingPatches
You'll need to resubmit your entire patch set with this
fixed up.
Thanks.
next prev parent reply other threads:[~2009-10-05 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 9:06 [net-next-2.6 PATCH 1/9] vxge: Modify __vxge_hw_device_is_privilaged() to not assume function-0 as privilaged function Sreenivasa Honnur
2009-10-05 9:20 ` David Miller [this message]
2009-10-05 9:40 ` Sreenivasa Honnur
2009-10-05 9:43 ` Sreenivasa Honnur
2009-10-05 9:48 ` David Miller
2009-10-05 10:07 ` Sreenivasa Honnur
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=20091005.022017.252887922.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Sreenivasa.Honnur@neterion.com \
--cc=netdev@vger.kernel.org \
--cc=support@neterion.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).