From: Jiri Slaby <jirislaby@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: writable limits into -next
Date: Mon, 19 Jul 2010 18:54:28 +0200 [thread overview]
Message-ID: <4C448344.9020807@gmail.com> (raw)
Hello,
could I ask you to include wrlimits tree into the -next. I refactored it
according to comments and will try to merge it on my own (as nobody is
willing to merge it apparently).
It's at:
git://decibel.fi.muni.cz/~xslaby/linux#writable_limits
There will be merge conflicts in unistd files with "unistd: add
__NR_prlimit64 syscall numbers". You can take a look at
http://decibel.fi.muni.cz/cgi-bin/gitweb.cgi?p=mm.git;a=shortlog;h=refs/heads/devel
to see how it looks like in -next.
thanks,
--
js
next reply other threads:[~2010-07-19 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 16:54 Jiri Slaby [this message]
2010-07-20 1:08 ` writable limits into -next Stephen Rothwell
2010-07-20 8:08 ` Jiri Slaby
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=4C448344.9020807@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.