From: David Miller <davem@davemloft.net>
To: erwanaliasr1@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
tshimizu818@gmail.com
Subject: Re: [PATCH] pch_gbe: Adding read memory barriers
Date: Mon, 07 May 2012 13:57:56 -0400 (EDT) [thread overview]
Message-ID: <20120507.135756.771396536686434223.davem@davemloft.net> (raw)
In-Reply-To: <4FA80B46.5070405@gmail.com>
Your patch doesn't apply to the net-next tree which is what you should
be basing all of your networking patches on:
[davem@bql net-next]$ git am --signoff pch_gbe-Adding-read-memory-barriers.patch
Applying: pch_gbe: Adding read memory barriers
error: patch failed: drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c:1222
error: drivers/net/ethernet/oki-semi/pch_gbe/pch_gbe_main.c: patch does not apply
Patch failed at 0001 pch_gbe: Adding read memory barriers
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".
Stop rushing things and take your time learning the process.
Otherwise you're going to make more work for maintainers and they
end up grumpy as a result, which you don't want.
next prev parent reply other threads:[~2012-05-07 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 17:49 [PATCH] pch_gbe: Adding read memory barriers Erwan Velu
2012-05-07 17:57 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-07 19:30 Erwan Velu
2012-05-08 18:35 ` Erwan Velu
2012-05-08 18:39 ` David Miller
2012-05-08 19:27 ` Erwan Velu
2012-05-09 10:47 ` David Laight
2012-05-09 13:18 ` Ben Hutchings
[not found] ` <CAL2JzuxirjAnmbcV+R=MJFAi1+ayrRnM6i0Dz5poqMuG7Cxwxg@mail.gmail.com>
2012-05-09 14:44 ` David Laight
[not found] ` <CAL2JzuxawnesC+=Fqyu71Hkwi5gnRughe_NYM4k1c=zqDoNGRg@mail.gmail.com>
2012-05-09 15:39 ` Ben Hutchings
2012-05-07 17:39 Erwan Velu
2012-05-07 17:44 ` David Miller
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=20120507.135756.771396536686434223.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=erwanaliasr1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tshimizu818@gmail.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).