From: Tim Cambrant <tim@cambrant.com>
To: Bryan Whitehead <driver@megahappy.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.2-rc1-mm3] fs/xfs/xfs_log_recover.c
Date: Sun, 25 Jan 2004 12:11:29 +0100 [thread overview]
Message-ID: <20040125111129.GA29501@cambrant.com> (raw)
In-Reply-To: <20040125044859.8A67F13A354@mrhankey.megahappy.net>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Sat, Jan 24, 2004 at 08:48:59PM -0800, Bryan Whitehead wrote:
> This patch keeps the same functionality but removes the warning the compiler generates.
I sent you a patch exactly like this a few days ago, but I don't know
if you got it. This way is a lot more simple than the approach you went
for in your last patch, but it really shouldn't matter at all. All it
does is to clear a warning. One tip though, in SubmittingPatches you
can read that the best way to create patches is by making them apply
with the -p1 flag. This is done by including the actual kernel source
directory when making the diff, such as this:
diff -up linux/fs/xfs/xfs_log_recover.c.orig linux/fs/xfs/xfs_log_recover.c
It doesn't matter what you named your kernel directory, since the -p1 flag
ignores that name. Using this command will improve your chances of getting
your patches included.
Tim Cambrant
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-25 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 4:48 [PATCH 2.6.2-rc1-mm3] fs/xfs/xfs_log_recover.c Bryan Whitehead
2004-01-25 11:11 ` Tim Cambrant [this message]
2004-01-25 21:31 ` Bryan Whitehead
2004-01-26 23:41 ` Nathan Scott
2004-01-27 0:09 ` Bryan Whitehead
2004-01-27 0:19 ` Nathan Scott
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=20040125111129.GA29501@cambrant.com \
--to=tim@cambrant.com \
--cc=driver@megahappy.net \
--cc=linux-kernel@vger.kernel.org \
/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