Re: [PATCH] kernel/hung_task.c: Monitor killed tasks.

[Tetsuo Handa]

On 2019/05/22 23:58, Tetsuo Handa wrote:
> On 2019/05/22 22:41, Stephen Rothwell wrote:
>> Hi Tetsuo,
>>
>> On Wed, 22 May 2019 21:38:45 +0900 Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx> wrote:
>>>
>>> I want to send debug printk() patches to linux-next.git. Petr Mladek
>>> is suggesting me to have a git tree for debug printk() patches.
>>> But it seems that there is "git quiltimport" command, and I prefer
>>> "subversion + quilt", and I don't have trees for sending "git pull"
>>> requests. Therefore, just ignoring "git quiltimport" failure is fine.
>>> What do you think?
>>
>> Sure, we can try.  I already have one quilt tree (besides Andrew's) in
>> linux-next, but much prefer a git tree.  If you have to use a quilt
>> tree, I will import it into a local branch on the base you tell me to
>> and then fetch it every morning and reimport it if it changes.  I will
>> then merge it like any other git branch.  Let me know what you can deal
>> with.
>>
> 
> What I do for making patches is:
> 
>   git fetch --tags
>   git reset --hard next-$date
>   edit files
>   git commit -a -s
>   git format-patch -1
>   git send-email --to=$recipient 0001-*.patch
> 
> I'm sure I will confuse git history/repository everyday if
> I try to send changes using git. For my skill level, managing
> 0001-*.patch in a subversion repository is the simplest and safest.
> 

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?