From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: Gavin Schenk <g.schenk@eckelmann.de>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] siox: don't create a thread without starting it
Date: Fri, 29 Jun 2018 09:38:58 +0200 [thread overview]
Message-ID: <20180629073858.5gwpfwqo2ccb4jaa@pengutronix.de> (raw)
In-Reply-To: <20180628075742.8991-1-u.kleine-koenig@pengutronix.de>
Hello Greg,
Cc -= Peter Zijlstra
Cc += Stephen Rothwell
On Thu, Jun 28, 2018 at 09:57:42AM +0200, Uwe Kleine-König wrote:
> Greg, you applied the initial patches creating drivers/siox. I assume
> you will continue to apply siox patches and tell if I should search a
> different path for these.
I put the two patches that I'd like to get in during the next merge
window into a branch in my repository:
https://git.pengutronix.de/git/ukl/linux siox/next
I assume you wouldn't object to add this branch to linux-next?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2018-06-29 7:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 10:20 [PATCH] RFC: " Uwe Kleine-König
2018-06-25 12:51 ` Peter Zijlstra
2018-06-25 19:21 ` Uwe Kleine-König
2018-06-26 7:31 ` Peter Zijlstra
2018-06-28 7:57 ` [PATCH] " Uwe Kleine-König
2018-06-28 8:18 ` Uwe Kleine-König
2018-06-29 6:27 ` Schenk, Gavin
2018-06-29 7:38 ` Uwe Kleine-König [this message]
2018-07-01 23:34 ` Stephen Rothwell
2018-07-02 0:40 ` Stephen Rothwell
2018-07-02 6:49 ` Uwe Kleine-König
2018-06-26 7:37 ` [PATCH] RFC: " Peter Zijlstra
2018-06-26 7:38 ` Peter Zijlstra
2018-06-28 8:03 ` Uwe Kleine-König
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=20180629073858.5gwpfwqo2ccb4jaa@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=g.schenk@eckelmann.de \
--cc=gregkh@suse.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®