Re: FAILED: patch "[PATCH] tracing: Free buffers when a used dynamic event is removed" failed to apply to 4.19-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 4 Dec 2022 17:34:15 +0100
Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:

> > > > > Depends-on: 5448d44c38557 ("tracing: Add unified dynamic event framework")    
> > > > 
> > > > ^^^    
> > > 
> > > Did you just make up a new field?  We have a documented way to show
> > > dependancies for stable patches, please let's not create a new one :(  
> > 
> > Ug, I've seen this tag used before: 
> > 
> >  example:  e3f0c638f428fd66b5871154b62706772045f91a
> > 
> > And just assumed that was the method. I guess I should have looked deeper.
> >   

I may need to denote patches again that are to be marked for stable but
depend on other commits. I'm looking for the "proper" way to do this so
that your scripts pick this up.

I searched Documentation for "depends" and the only thing I see in there is
in Documentation/process/submitting-patches.rst:

   If one patch depends on another patch in order for a change to be
   complete, that is OK.  Simply note **"this patch depends on patch X"**
   in your patch description.

But that looks to be used for a patch that depends on some other patch in
the series. I'm doing something that will depend on an existing commit. And
do your scripts pick up on that line anyway?

Where's this documented way to show dependencies for stable patches?

-- Steve




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux