From: Russell King <rmk@arm.linux.org.uk>
To: DervishD <raul@pleyades.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] mmap.c (do_mmap_pgoff), against 2.4.19 and 2.4.20-pre10
Date: Mon, 14 Oct 2002 11:09:47 +0100 [thread overview]
Message-ID: <20021014110947.B32186@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20021014093622.GA96@DervishD>; from raul@pleyades.net on Mon, Oct 14, 2002 at 11:36:22AM +0200
On Mon, Oct 14, 2002 at 11:36:22AM +0200, DervishD wrote:
> Well, the attachments included (unified diff format), is the patch
> against both 2.4.19 and 2.4.20-pre10 (I've changed the kernel name
> directory part to '/usr/src/linux/' so it's applicable to both
> versions.
You could try sending a patch that conforms to the following (why don't
we include a comment about this in Documentation/SubmittingPatches?)
This would remove an extra reason why your patch may not have been
accepted.
PATCH(1) PATCH(1)
NAME
patch - apply a diff file to an original
...
NOTES FOR PATCH SENDERS
There are several things you should bear in mind if you
are going to be sending out patches.
...
If the recipient is supposed to use the -pN option, do not
send output that looks like this:
diff -Naur v2.0.29/prog/README prog/README
--- v2.0.29/prog/README Mon Mar 10 15:13:12 1997
+++ prog/README Mon Mar 17 14:58:22 1997
because the two file names have different numbers of
slashes, and different versions of patch interpret the
file names differently.
Content-Description: mmap.c.diff
> --- /usr/src/linux/mm/mmap.c.orig 2002-10-14 11:16:40.000000000 +0200
> +++ /usr/src/linux/kernel/mm/mmap.c 2002-10-14 11:19:32.000000000 +0200
Also, you should generate the patches without the "/usr/src/" prefix.
So it should look like this:
--- linux/mm/mmap.c.orig 2002-10-14 11:16:40.000000000 +0200
+++ linux/mm/mmap.c 2002-10-14 11:19:32.000000000 +0200
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-10-14 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 9:36 [PATCH] mmap.c (do_mmap_pgoff), against 2.4.19 and 2.4.20-pre10 DervishD
2002-10-14 9:52 ` David S. Miller
2002-10-14 10:20 ` DervishD
2002-10-14 10:44 ` David S. Miller
2002-10-14 11:04 ` DervishD
2002-10-14 10:09 ` Russell King [this message]
2002-10-14 10:25 ` DervishD
2002-10-14 20:26 ` Marcelo Tosatti
2002-10-15 7:37 ` DervishD
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=20021014110947.B32186@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=raul@pleyades.net \
/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).