All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: RMK closing tree to patches *this* weekend
Date: Mon, 17 May 2010 16:44:20 +0100	[thread overview]
Message-ID: <000301caf5d7$d15bab60$74130220$@deacon@arm.com> (raw)
In-Reply-To: <20100517151036.GE29422@n2100.arm.linux.org.uk>

Hi Russell,

> Therefore, this "initial batch" is most likely to become "only batch"
> since it's no longer possible to be reasonably ensure that there will
> be a merge window open in the second week.

If this is likely to be the case, will the OProfile patches be merged
during this batch? The reason I ask is because they have been applied to
the `devel-pmu' branch, but I can't find this in your repository. I also
can't see the patches in any of your other branches.

Knowing when the Kernel patches will be going in helps me to co-ordinate
submission of the accompanying userspace patches.

Thanks,

Will

  reply	other threads:[~2010-05-17 15:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 23:02 RMK closing tree to patches *this* weekend Russell King - ARM Linux
2010-05-14  0:35 ` Ben Dooks
2010-05-14  9:20   ` Russell King - ARM Linux
2010-05-14  0:58 ` Jassi Brar
2010-05-14  9:24   ` Russell King - ARM Linux
2010-05-14 14:21     ` Jassi Brar
2010-05-14  2:09 ` Ming Lei
2010-05-14  9:27 ` Russell King - ARM Linux
2010-05-17  9:03 ` Russell King - ARM Linux
2010-05-17 13:04   ` Nicolas Pitre
2010-05-17 13:08     ` Russell King - ARM Linux
2010-05-17 15:10     ` Russell King - ARM Linux
2010-05-17 15:44       ` Will Deacon [this message]
2010-05-17 16:18         ` Russell King - ARM Linux

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='000301caf5d7$d15bab60$74130220$@deacon@arm.com' \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.