From: Roel Kluin <12o3l@tiscali.nl>
To: Jeff Dike <jdike@addtoit.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] use array_size macro
Date: Fri, 28 Sep 2007 16:45:06 +0200 [thread overview]
Message-ID: <46FD1372.70608@tiscali.nl> (raw)
In-Reply-To: <20070928131514.GA5209@c2.user-mode-linux.org>
Jeff Dike wrote:
> On Fri, Sep 28, 2007 at 12:56:31PM +0200, Roel Kluin wrote:
>> arch/um/kernel/tt/ptproxy/ptrace.c | 12 ++++++------
>
> I don't know what you're diffing against, but this file is history in
> -mm, and will be gone in mainline after 2.6.23.
>
> Jeff
>
Thanks for noting me. I usually pull the masters branch, so my previously submitted
patches are against that. Apparently I have to apply the -mm patchset before sending
patches. Is there a git branch to pull from for that?
Roel
next prev parent reply other threads:[~2007-09-28 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 10:48 [PATCH] use array_size macro Roel Kluin
2007-09-28 10:56 ` Roel Kluin
2007-09-28 13:15 ` Jeff Dike
2007-09-28 14:45 ` Roel Kluin [this message]
2007-09-28 16:24 ` Randy Dunlap
2007-09-28 16:46 ` Jeff Dike
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=46FD1372.70608@tiscali.nl \
--to=12o3l@tiscali.nl \
--cc=jdike@addtoit.com \
--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