From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] make dt_scan_depth1_nodes more readable
Date: Mon, 25 Apr 2016 12:19:38 +0100 [thread overview]
Message-ID: <20160425111938.GK16065@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1604251204380.24872@sstabellini-ThinkPad-X260>
On Mon, Apr 25, 2016 at 12:04:53PM +0100, Stefano Stabellini wrote:
> On Mon, 25 Apr 2016, Will Deacon wrote:
> > On Mon, Apr 25, 2016 at 11:25:11AM +0100, Stefano Stabellini wrote:
> > > From: Mark Rutland <mark.rutland@arm.com>
> > >
> > > Improve the readability of dt_scan_depth1_nodes by removing the nested
> > > conditionals.
> > >
> > > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > > Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
> > >
> > > ---
> > >
> > > Note: this patch is based on xentip/for-linus-4.7
> >
> > So how should I merge it? :/
>
> I think that if you would like to merge it, it would be easier this time
> for me to carry it in my tree. Otherwise you would have to base your
> for-linus-4.7 on xentip/for-linus-4.7 and send the pull request after
> the Xen pull request -- undesirable.
Ok, doesn't look like we'll run into conflicts. I just find it weird that
you'd have a patch with no functional change as a dependency, hence my
preference to queue it in the arm64 tree (where conflicts are more likely).
Will
next prev parent reply other threads:[~2016-04-25 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 10:25 [PATCH] make dt_scan_depth1_nodes more readable Stefano Stabellini
2016-04-25 10:53 ` Will Deacon
2016-04-25 11:04 ` Stefano Stabellini
2016-04-25 11:19 ` Will Deacon [this message]
2016-04-25 11:24 ` Stefano Stabellini
2016-04-25 12:54 ` Will Deacon
2016-04-25 12:56 ` Stefano Stabellini
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=20160425111938.GK16065@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 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).