linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] arm/arm64: add arm-smccc
Date: Mon, 4 Jan 2016 11:11:02 +0000	[thread overview]
Message-ID: <20160104111102.GA19062@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160104101323.GA24963@red-moon>

On Mon, Jan 04, 2016 at 10:13:39AM +0000, Lorenzo Pieralisi wrote:
> Hi Russell,
> 
> On Tue, Dec 22, 2015 at 12:14:49PM +0000, Russell King - ARM Linux wrote:
> > Okay, I think as we don't have a decision on this, the proximity of
> > Christmas, and the presumable opening of the merge window early in
> > the new year, I can't merge these patches for the upcoming window.
> > I'll discard those which have already been submitted to the patch
> > system.
> > 
> > This also has a knock-on effect on patch 8486/1:
> > 
> > "ARM64: kernel: PSCI: move PSCI idle management code to drivers/firmware"
> > 
> > which is based on top of this series.  If someone wants to replace
> > that patch with one which has been tested _without_ this series
> > then I'll look at applying it, provided its only trivially different
> > from the existing one.
> 
> I guess Jens' patches are not considered material for the upcoming merge
> window, would you consider applying an updated version of 8486/1 (that does
> not depend on Jens' series) or it is too late ? That patch has already
> missed a merge window for patch dependencies, I would avoid another one,
> I appreciate the timing is not ideal though, please let me know.

The reason I said what I did above was to head-off the merge window
opening last night, and having a rushed job dealing with problems
with patches merged at the last minute.

Consider that the period 24th December to 3rd January does not exist
for many as far as working on the kernel is concerned, and linux-next
probably wasn't running over that period either.

The situation has changed though; last night, Linus released -rc8,
which means we have one week of breathing space before the merge window
is likely to open, and we have four days of linux-next trees.

This means that I'm willing to take patches today (and today only), as
it will give the remainder of the week (up to Thursday - due to the
linux-next timing) to sort out any deficiencies in those patches.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2016-01-04 11:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 13:24 [PATCH v6] arm/arm64: add arm-smccc Jens Wiklander
2015-12-21 11:14 ` Lorenzo Pieralisi
2015-12-22  9:46   ` Jens Wiklander
2015-12-22 12:14     ` Russell King - ARM Linux
2016-01-04 10:13       ` Lorenzo Pieralisi
2016-01-04 11:11         ` Russell King - ARM Linux [this message]
2016-01-04 11:16           ` Russell King - ARM Linux
2016-01-04 12:22             ` Lorenzo Pieralisi
2016-01-04 12:14     ` Lorenzo Pieralisi
2016-01-04 12:26       ` Jens Wiklander

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=20160104111102.GA19062@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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 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).