From: Stephen Rothwell <sfr@canb.auug.org.au>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: mmotm 2013-06-05-17-24 uploaded
Date: Thu, 6 Jun 2013 12:04:55 +1000 [thread overview]
Message-ID: <20130606120455.bd86a4c0ac009482db80f634@canb.auug.org.au> (raw)
In-Reply-To: <20130606002636.6746F5A41AE@corp2gmr1-2.hot.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
Hi Andrew,
On Wed, 05 Jun 2013 17:26:36 -0700 akpm@linux-foundation.org wrote:
>
> linux-next-git-rejects.patch
We must figure out why you sometimes get rejects that I do not get when I
import your series into a git tree. However in this case you resolution
is not quite right. It leaves 2 continue statements in
net/mac80211/iface.c at line 191 which will unconditionally short circuit
the enclosing loop. The version that will be in linux-next today is
correct (and git did it automatically as part of the merge of the old
linux-next tree).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-06 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 0:26 mmotm 2013-06-05-17-24 uploaded akpm
2013-06-06 2:04 ` Stephen Rothwell [this message]
2013-06-06 7:23 ` Geert Uytterhoeven
2013-06-06 7:37 ` Stephen Rothwell
2013-06-06 4:31 ` mmotm 2013-06-05-17-24 uploaded (rtc) Randy Dunlap
2013-06-06 20:07 ` Andrew Morton
2013-06-06 4:37 ` mmotm 2013-06-05-17-24 uploaded (ptp_pch) Randy Dunlap
2013-06-06 19:51 ` Ben Hutchings
2013-06-06 11:40 ` mmotm 2013-06-05-17-24 uploaded Robin Holt
2013-06-06 16:25 ` mmotm 2013-06-05-17-24 uploaded (sound/soc/codecs/adav80x) Randy Dunlap
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=20130606120455.bd86a4c0ac009482db80f634@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mm-commits@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;
as well as URLs for NNTP newsgroup(s).