From: Russell King <rmk@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: daniel.ritz@gmx.ch, netdev@oss.sgi.com
Subject: Re: [PATCH] fix arm/etherh.c allocation
Date: Thu, 22 Apr 2004 08:33:42 +0100 [thread overview]
Message-ID: <20040422083342.A31406@flint.arm.linux.org.uk> (raw)
In-Reply-To: <40873BEA.1040208@pobox.com>; from jgarzik@pobox.com on Wed, Apr 21, 2004 at 11:28:42PM -0400
On Wed, Apr 21, 2004 at 11:28:42PM -0400, Jeff Garzik wrote:
> Daniel Ritz wrote:
> > --- 1.23/drivers/net/arm/etherh.c Wed Apr 14 12:23:55 2004
> > +++ edited/etherh.c Tue Apr 20 20:39:04 2004
>
>
> can one of you resend something that applies with 'patch -sp1'?
I've noticed this as well - I just end up fixing the patch headers
manually. It's a BK bug unfortunately - if you provide a directory
for bk diffs, it messes up like above, but if you give explicit files
it doesn't.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
prev parent reply other threads:[~2004-04-22 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 18:49 [PATCH] fix arm/etherh.c allocation Daniel Ritz
2004-04-22 3:28 ` Jeff Garzik
2004-04-22 7:33 ` Russell King [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=20040422083342.A31406@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=daniel.ritz@gmx.ch \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).