From: Peter Zijlstra <peterz@infradead.org>
To: "Ofer Levi(SW)" <oferle@mellanox.com>
Cc: "rusty@rustcorp.com.au" <rusty@rustcorp.com.au>,
"mingo@redhat.com" <mingo@redhat.com>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: hotplug support for arch/arc/plat-eznps platform
Date: Thu, 10 Aug 2017 11:19:05 +0200 [thread overview]
Message-ID: <20170810091905.4lekz7gtjprbgiyn@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <VI1PR0501MB2110C116B9791B98D2E0C0ECB2880@VI1PR0501MB2110.eurprd05.prod.outlook.com>
On Thu, Aug 10, 2017 at 07:40:16AM +0000, Ofer Levi(SW) wrote:
> Well, this definitely have pleased the little toy :)
> Thank you. I really appreciate your time and effort.
>
> If I may, one more newbie question. What do I need to do for the two patches to find
> their way into formal kernel code?
I'll split the first patch into two separate patches and line them up.
I'm not sure about this last patch, I'll speak with Ingo once he's back
to see what would be the thing to do here.
I suspect we can make it work, that sysctl stuff is only debug crud
after all and that should never get in the way of getting work done.
next prev parent reply other threads:[~2017-08-10 9:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 5:53 Ofer Levi(SW)
2017-08-07 8:33 ` Peter Zijlstra
2017-08-07 13:41 ` Ofer Levi(SW)
2017-08-07 15:10 ` Peter Zijlstra
2017-08-08 6:49 ` Ofer Levi(SW)
2017-08-08 10:16 ` Peter Zijlstra
2017-08-09 15:19 ` Ofer Levi(SW)
2017-08-09 15:34 ` Peter Zijlstra
2017-08-10 7:40 ` Ofer Levi(SW)
2017-08-10 9:19 ` Peter Zijlstra [this message]
2017-08-10 11:51 ` Ofer Levi(SW)
2017-08-10 15:45 ` Peter Zijlstra
2017-08-14 7:54 ` Ofer Levi(SW)
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=20170810091905.4lekz7gtjprbgiyn@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oferle@mellanox.com \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®