From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Rosin <peda@axentia.se>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST] mux for 4.12
Date: Mon, 27 Mar 2017 11:49:56 +0200 [thread overview]
Message-ID: <20170327094956.GA8456@kroah.com> (raw)
In-Reply-To: <5edd04ce-5914-8cde-aab6-fc7e18dcf282@axentia.se>
On Mon, Mar 27, 2017 at 10:30:44AM +0200, Peter Rosin wrote:
> Hi Greg,
>
> Today seemed like a good day to send you the pull request for the new mux
> controller subsystem. I hope the details are ok. If not, let me know and
> I'll try to rework it. I also included some text for the merge commit, if
> you want/need it:
Can you please just send me patches, so that people cna review them,
including myself? I only pull from a very small group of people, and
only from kernel.org accounts. Brand new subsystems need to be sent as
patches, sorry.
Have all of the needed subsystem maintainers signed off on these patches
already as well?
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-27 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 8:30 [PULL REQUEST] mux for 4.12 Peter Rosin
2017-03-27 9:49 ` Greg Kroah-Hartman [this message]
2017-03-27 11:25 ` Peter Rosin
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=20170327094956.GA8456@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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