All of lore.kernel.org
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] arm/arm64: add arm-smccc
Date: Mon, 4 Jan 2016 12:22:51 +0000	[thread overview]
Message-ID: <20160104122251.GB698@red-moon> (raw)
In-Reply-To: <20160104111627.GB19062@n2100.arm.linux.org.uk>

On Mon, Jan 04, 2016 at 11:16:27AM +0000, Russell King - ARM Linux wrote:
> On Mon, Jan 04, 2016 at 11:11:02AM +0000, Russell King - ARM Linux wrote:
> > 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.
> 
> That all said, 8486/1 _is_ the patch you've just asked me to merge,
> which has open questions from Jens that you (Lorenzo) have _not_
> responded to.
> 
> Jens was asking, in response to your feedback, whether an alternative
> Kconfig structure would satisfy your feedback... to which he's had no
> reply from you.  So, we're waiting on your response.

Sorry for the delay in replying. I re-tested 8486/1 on top of Jens'
v7, it is all fine, I commented on the config structure which is
a change that does not affect 8486/1 so if it is ok with you I am happy
for 8486/1 to be applied on top of Jens' series (I guess he should be
sending a v8 today which should be final).

As a heads-up, 8486/1 also depends on 8485/1 that you have already applied.

Thanks,
Lorenzo

  reply	other threads:[~2016-01-04 12:22 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
2016-01-04 11:16           ` Russell King - ARM Linux
2016-01-04 12:22             ` Lorenzo Pieralisi [this message]
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=20160104122251.GB698@red-moon \
    --to=lorenzo.pieralisi@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.