linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Kuo <rkuo@codeaurora.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-hexagon@vger.kernel.org,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Michal Marek <mmarek@suse.com>, Sam Ravnborg <sam@ravnborg.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hexagon: get rid of #include <generated/compile.h>
Date: Mon, 9 Oct 2017 11:31:42 -0500	[thread overview]
Message-ID: <20171009163142.GA19621@codeaurora.org> (raw)
In-Reply-To: <CAK7LNARd6ovx=qmny1micPx7BUXf9uL9soES_OcotF-bYCCQWw@mail.gmail.com>

On Mon, Oct 09, 2017 at 11:25:28PM +0900, Masahiro Yamada wrote:
> >>
> >
> > How should this patch be handled?
> >
> 
> I checked
> git://git.kernel.org/pub/scm/linux/kernel/git/rkuo/linux-hexagon-kernel.git
> 
> I could not see any patch applied to the tree since last year.
> 
> Assuming the tree is unmaintained, I am picking this patch to Kbuild tree.
> 
> 
> 
> Applied to linux-kbuild/kbuild with Rechard's Acked.
> 
> 
> 
> -- 
> Best Regards
> Masahiro Yamada


Sorry about that.  For the record I'm fine with these patches going up
some of the other trees, like trivial or kbuild.  Might go faster that way.


Thanks,
Richard Kuo




-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, 
a Linux Foundation Collaborative Project

      reply	other threads:[~2017-10-09 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 15:17 [PATCH] hexagon: get rid of #include <generated/compile.h> Masahiro Yamada
2017-09-27 23:24 ` Richard Kuo
2017-10-03  1:26   ` Masahiro Yamada
2017-10-09 14:25     ` Masahiro Yamada
2017-10-09 16:31       ` Richard Kuo [this message]

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=20171009163142.GA19621@codeaurora.org \
    --to=rkuo@codeaurora.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=oleg@redhat.com \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).