mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: replace arm64-obj-* in Makefile with obj-*
Date: Fri, 14 Dec 2018 10:37:21 +0000	[thread overview]
Message-ID: <20181214103721.GC1872@edgewater-inn.cambridge.arm.com> (raw)
In-Reply-To: <CAK7LNATTGxopJJsj=sakmqxwpyETgG7ToS8tm4kLcF2jekNcFw@mail.gmail.com>

On Fri, Dec 14, 2018 at 07:35:57PM +0900, Masahiro Yamada wrote:
> Hi Will,
> 
> On Fri, Dec 14, 2018 at 6:54 PM Will Deacon <will.deacon@arm.com> wrote:
> >
> > Hi Masahiro,
> >
> > On Fri, Dec 14, 2018 at 01:01:52PM +0900, Masahiro Yamada wrote:
> > > Use the standard obj-$(CONFIG_...) syntex. The behavior is still the
> > > same.
> > >
> > > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > > ---
> > >
> > >  arch/arm64/kernel/Makefile | 59 +++++++++++++++++++++++-----------------------
> > >  1 file changed, 29 insertions(+), 30 deletions(-)
> >
> > I'm fine with this patch, but I think I'd prefer to apply it at -rc1 so
> > we don't end up with lots of silly conflicts in the Makefile for any new
> > files added during the merge window.
> >
> > Is that ok with you?
> 
> Sure!

Brill. Please poke me again in January if it hasn't landed by then ;)

Will

  reply	other threads:[~2018-12-14 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  4:01 Masahiro Yamada
2018-12-14  9:51 ` Will Deacon
2018-12-14 10:35   ` Masahiro Yamada
2018-12-14 10:37     ` Will Deacon [this message]
2019-01-04  0:24       ` Masahiro Yamada

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=20181214103721.GC1872@edgewater-inn.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamada.masahiro@socionext.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

all inboxes | Powered by JetHome®