linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Joe Perches <joe@perches.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	"Wang, Yalin" <Yalin.Wang@sonymobile.com>,
	'Will Deacon' <will.deacon@arm.com>,
	'Ard Biesheuvel' <ard.biesheuvel@linaro.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'akinobu.mita@gmail.com'" <akinobu.mita@gmail.com>,
	"'linux-mm@kvack.org'" <linux-mm@kvack.org>,
	"'linux-arm-kernel@lists.infradead.org'"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC V6 2/3] arm:add bitrev.h file to support rbit instruction
Date: Fri, 14 Nov 2014 09:52:06 +0000	[thread overview]
Message-ID: <20141114095205.GF4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1415928394.4141.3.camel@perches.com>

On Thu, Nov 13, 2014 at 05:26:34PM -0800, Joe Perches wrote:
> On Fri, 2014-11-14 at 01:18 +0000, Russell King - ARM Linux wrote:
> > On Thu, Nov 13, 2014 at 04:45:43PM -0800, Joe Perches wrote:
> > > I think you shouldn't apply these patches or updated
> > > ones either until all the current uses are converted.
> > 
> > Where are the dependencies mentioned?
> 
> I mentioned it when these patches (which are not
> mine btw), were submitted the second time.

Yes, I'm well aware that the author of the ARM patches are Yalin Wang.

> https://lkml.org/lkml/2014/10/27/69
> 
> > How do I get to know when all
> > the dependencies are met?
> 
> No idea.
> 
> > Who is tracking the dependencies?
> 
> Not me.

Right, what that means is that no one is doing that.  What you've also
said in this thread now is that the ARM patches should not be applied
until all the other users are converted.  As those patches are going via
other trees, that means the ARM patches can only be applied _after_ the
next merge window _if_ all maintainers pick up the previous set.

As I'm not tracking the status of what other maintainers do, I'm simply
going to avoid applying these patches until after the next merge window
and hope that the other maintainers pick the dependent patches up and get
them in during the next merge window.  If not, I guess we'll see compile
breakage.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-11-14  9:52 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  5:10 [PATCH RFC] arm/arm64:add CONFIG_HAVE_ARCH_BITREVERSE to support rbit Wang, Yalin
2014-10-27  6:37 ` [RFC V2] arm/arm64:add CONFIG_HAVE_ARCH_BITREVERSE to support rbit instruction Wang, Yalin
2014-10-27  6:46   ` Joe Perches
2014-10-27  7:13     ` Wang, Yalin
2014-10-28 21:18     ` [PATCH] carl9170: Convert byte_rev_table uses to bitrev8 Joe Perches
2014-10-28 21:22     ` [PATCH] 6fire: " Joe Perches
2014-10-29  2:42       ` Wang, Yalin
2014-10-29  3:06         ` Joe Perches
2014-10-29  3:10           ` Wang, Yalin
2014-10-29  3:28     ` [RFC V2] arm/arm64:add CONFIG_HAVE_ARCH_BITREVERSE to support rbit instruction Rob Herring
2014-10-29  5:14       ` [RFC V4 1/3] add " Wang, Yalin
2014-10-29  5:15         ` [RFC V4 2/3] arm:add bitrev.h file " Wang, Yalin
2014-10-29  5:16           ` [RFC V4 3/3] arm64:add " Wang, Yalin
2014-10-29  5:50             ` [RFC V5 1/3] add CONFIG_HAVE_ARCH_BITREVERSE " Wang, Yalin
2014-10-29  5:51               ` [RFC V5 2/3] arm:add bitrev.h file " Wang, Yalin
2014-10-29  5:52                 ` [RFC V5 3/3] arm64:add " Wang, Yalin
2014-10-30 12:01                   ` Will Deacon
2014-10-30 12:26                     ` Ard Biesheuvel
2014-10-30 13:57                       ` Will Deacon
2014-10-31  5:40                         ` [RFC V6 1/3] add CONFIG_HAVE_ARCH_BITREVERSE " Wang, Yalin
2014-10-31  5:40                           ` [RFC V6 2/3] " Wang, Yalin
2014-10-31  5:42                             ` [RFC V6 2/3] arm:add bitrev.h file " Wang, Yalin
2014-10-31  7:40                               ` [RFC] arm:remove clear_thread_flag(TIF_UPROBE) Wang, Yalin
2014-10-31  7:45                                 ` Joe Perches
2014-10-31  7:51                                   ` Wang, Yalin
2014-10-31  7:58                                     ` Joe Perches
2014-10-31  7:59                                       ` Wang, Yalin
2014-10-31  8:01                                     ` [RFC V2] " Wang, Yalin
2014-11-13 23:53                               ` [RFC V6 2/3] arm:add bitrev.h file to support rbit instruction Russell King - ARM Linux
2014-11-14  0:05                                 ` Joe Perches
2014-11-14  0:17                                   ` Russell King - ARM Linux
2014-11-14  0:45                                     ` Joe Perches
2014-11-14  1:18                                       ` Russell King - ARM Linux
2014-11-14  1:26                                         ` Joe Perches
2014-11-14  9:52                                           ` Russell King - ARM Linux [this message]
2014-11-14  6:37                                   ` Takashi Iwai
2014-11-14  6:55                                     ` Joe Perches
2014-11-14  7:03                                       ` Takashi Iwai
2014-11-14  2:01                                 ` Wang, Yalin
2014-11-14  9:58                                   ` Russell King - ARM Linux
2014-11-17  2:38                                     ` Wang, Yalin
2015-01-08 18:40                                       ` Russell King - ARM Linux
2015-01-09  2:16                                         ` Wang, Yalin
2015-01-09 11:10                                           ` Russell King - ARM Linux
2015-01-09 12:40                                             ` Wang, Yalin
2015-01-14 16:38                                               ` Russell King - ARM Linux
2015-01-16  1:42                                                 ` Wang, Yalin
2014-10-31  7:54                             ` [RFC V6 2/3] add CONFIG_HAVE_ARCH_BITREVERSE " Wang, Yalin
2014-10-31  5:41                           ` [RFC V6 3/3] arm64:add bitrev.h file " Wang, Yalin
2014-10-31 10:43                             ` Will Deacon
2014-11-03  2:17                               ` Wang, Yalin
2014-11-03  8:47                                 ` Ard Biesheuvel
2014-11-03  9:50                                   ` Will Deacon
2014-11-04  1:45                                     ` Wang, Yalin
2014-10-31  2:03                     ` [RFC V5 " Wang, Yalin
2014-10-29  5:21         ` [RFC V4 1/3] add CONFIG_HAVE_ARCH_BITREVERSE " Joe Perches
2014-10-29  5:36           ` Wang, Yalin
2014-10-29  5:20       ` [RFC V2] arm/arm64:add " Wang, Yalin
2014-10-27  8:02   ` [RFC V3] " Wang, Yalin
2014-10-27 10:48     ` Will Deacon
2014-10-28  1:34       ` Wang, Yalin
2014-10-28 13:59         ` Will Deacon
2014-10-29  2:52           ` Wang, Yalin

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=20141114095205.GF4042@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=Yalin.Wang@sonymobile.com \
    --cc=akinobu.mita@gmail.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=joe@perches.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tiwai@suse.de \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).