[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190522144300.5ea06345efd9a831803105b7@linux-foundation.org>
Date: Wed, 22 May 2019 14:43:00 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Petr Mladek <pmladek@...e.com>, Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...ux.ibm.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Liu Chuansheng <chuansheng.liu@...el.com>,
Valdis Kletnieks <valdis.kletnieks@...edu>,
linux-kernel@...r.kernel.org, Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [PATCH] kernel/hung_task.c: Monitor killed tasks.
On Thu, 23 May 2019 07:39:25 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > I put an example patch into my subversion repository:
> >
> > svn checkout https://svn.osdn.net/svnroot/tomoyo/branches/syzbot-patches/
> >
> > To fetch up-to-date debug printk() patches:
> >
> > cd syzbot-patches
> > svn update
> >
> > Does this work for you?
>
> Neither will fit into my normal workflow.
>
> So, tell me, what are you trying to do? What does you work depend on?
> Just Linus' tree, or something already in linux-next? Why would you
> want to keep moving your patch(es) on top of linux-next?
um, I can carry developer-only linux-next debug patches.
Powered by blists - more mailing lists