From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: linux-mips@linux-mips.org, linux-doc@vger.kernel.org,
jcmvbkbc@gmail.com, harryxiyou@gmail.com, paulus@samba.org,
linux@arm.linux.org.uk, richard@nod.at,
linux-xtensa@linux-xtensa.org, rob@landley.net,
user-mode-linux-devel@lists.sourceforge.net, jdike@addtoit.com,
xiyoulinuxkernelgroup@googlegroups.com,
user-mode-linux-user@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org, chris@zankel.net,
isdn@linux-pingi.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, ralf@linux-mips.org,
linux-kernel@zh-kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V2] wanrouter: Remove it and the drivers that depend on it
Date: Tue, 13 Nov 2012 14:32:41 -0800 [thread overview]
Message-ID: <1352845961.17444.13.camel@joe-AO722> (raw)
In-Reply-To: <20121113.171736.561094209116852795.davem@davemloft.net>
On Tue, 2012-11-13 at 17:17 -0500, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Tue, 13 Nov 2012 12:17:25 -0800
>
> > That seems an odd workflow as it leaves dangling CONFIG_<foo>
> > options set, but I guess it doesn't hurt so here it is.
>
> As you said it's harmless, and more importantly it avoids
> unnecessary conflicts.
>
> > I just removed the modified arch/.../<foo>defconfig files.
>
> Something is not right here:
> [davem@drr net-next]$ git am --signoff V2-wanrouter-Remove-it-and-the-drivers-that-depend-on-it.patch
> Applying: wanrouter: Remove it and the drivers that depend on it
> error: removal patch leaves file contents
> error: net/wanrouter/Kconfig: patch does not apply
> error: removal patch leaves file contents
> error: net/wanrouter/Makefile: patch does not apply
> error: removal patch leaves file contents
> error: net/wanrouter/patchlevel: patch does not apply
> error: removal patch leaves file contents
> error: net/wanrouter/wanmain.c: patch does not apply
> error: removal patch leaves file contents
> error: net/wanrouter/wanproc.c: patch does not apply
> error: removal patch leaves file contents
> error: drivers/net/wan/cycx_drv.c: patch does not apply
> error: removal patch leaves file contents
> error: drivers/net/wan/cycx_main.c: patch does not apply
> error: removal patch leaves file contents
> error: drivers/net/wan/cycx_x25.c: patch does not apply
> error: removal patch leaves file contents
> error: include/linux/cyclomx.h: patch does not apply
> error: removal patch leaves file contents
> error: include/linux/cycx_drv.h: patch does not apply
> error: removal patch leaves file contents
> error: include/linux/wanrouter.h: patch does not apply
> error: removal patch leaves file contents
> error: include/uapi/linux/wanrouter.h: patch does not apply
Right, that is unexpected/odd/interesting.
I was trying to save mailing list bandwidth by reducing
the patch size.
I generated this with
$ git format-patch -M -D
but it doesn't apply here either. :(
Using
$ git format-patch -M
does apply correctly.
It's quite a bit larger though. (120KB vs 14)
I'll send the large patch just to netdev.
Joe
prev parent reply other threads:[~2012-11-13 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 14:20 [PATCH] wanrouter: Remove it and the drivers that depend on it Joe Perches
2012-11-13 19:44 ` David Miller
2012-11-13 20:17 ` [PATCH V2] " Joe Perches
2012-11-13 22:17 ` David Miller
2012-11-13 22:32 ` Joe Perches [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=1352845961.17444.13.camel@joe-AO722 \
--to=joe@perches.com \
--cc=chris@zankel.net \
--cc=davem@davemloft.net \
--cc=harryxiyou@gmail.com \
--cc=isdn@linux-pingi.de \
--cc=jcmvbkbc@gmail.com \
--cc=jdike@addtoit.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kernel@zh-kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
--cc=xiyoulinuxkernelgroup@googlegroups.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).