[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180702064926.sxx4wj5mxiywxkva@pengutronix.de>
Date: Mon, 2 Jul 2018 08:49:26 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Gavin Schenk <g.schenk@...elmann.de>,
linux-kernel@...r.kernel.org, kernel@...gutronix.de
Subject: Re: [PATCH] siox: don't create a thread without starting it
Hello,
On Mon, Jul 02, 2018 at 09:34:04AM +1000, Stephen Rothwell wrote:
> On Fri, 29 Jun 2018 09:38:58 +0200 Uwe Kleine-König <u.kleine-koenig@...gutronix.de> wrote:
> >
> > 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?
>
> Added from today.
Ok, great.
> Is this a continuing effort, or should I just remove the tree once
> Greg has merged it?
I expect the patch count to be zero for most future releases because
there are probably no users apart from Eckelmann. On the other hand if
we still need a patch it would continue to be good to have the exposure
in next.
So I'd say, if it reduces your burden feel free to drop it and if there
is something relevant later, it seems to be easy enough to readd it
then.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Powered by blists - more mailing lists