From: Andrew Morton <akpm@linux-foundation.org>
To: Arun Sharma <asharma@fb.com>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH 2/2] atomic: move atomic_add_unless to generic code
Date: Tue, 7 Jun 2011 16:48:35 -0700 [thread overview]
Message-ID: <20110607164835.86fa15f4.akpm@linux-foundation.org> (raw)
In-Reply-To: <4DE7C6FF.70108@fb.com>
On Thu, 02 Jun 2011 10:23:11 -0700
Arun Sharma <asharma@fb.com> wrote:
> On 6/2/11 7:53 AM, Mike Frysinger wrote:
>
> >> The idea is to move atomic_add_unless_return() into linux/atomic.h
> >
> > my point is that that patchset doesnt seem to exist yet, and it'd
> > probably make sense to have it ready and part of this series before
> > attempting to push this.
>
> I posted the patch a couple of days ago:
>
> 1306889876-5327-1-git-send-email-asharma@fb.com
> http://thread.gmane.org/gmane.linux.kernel/1148420
>
This is way too hard. Please send the *entire* patchset with full
descriptions in the changelogs. Not referring to kooky MessageID's, no
links to archives which might be removed. Aim to have a complete,
well-presented patchset which our children can as-easily-as-possible
understand when they read the git commit logs in 2042.
next prev parent reply other threads:[~2011-06-07 23:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:10 [PATCH 1/2] atomic: use <linux/atomic.h> Arun Sharma
2011-05-31 19:10 ` [PATCH 2/2] atomic: move atomic_add_unless to generic code Arun Sharma
2011-05-31 20:21 ` Mike Frysinger
2011-05-31 21:17 ` Arun Sharma
2011-06-02 14:53 ` Mike Frysinger
2011-06-02 17:23 ` Arun Sharma
2011-06-07 23:48 ` Andrew Morton [this message]
2011-06-08 0:42 ` Arun Sharma
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=20110607164835.86fa15f4.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=asharma@fb.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vapier.adi@gmail.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