Re: [PATCH] docs: submitting-patches: improve the base commit explanation

2023-11-27 Thread Jonathan Corbet
Borislav Petkov writes: > From: "Borislav Petkov (AMD)" > > After receiving a second patchset this week without knowing which tree > it applies on and trying to apply it on the obvious ones and failing, > make sure the base tree information which needs to be supplied in the > 0th message of the

Re: [PATCH] docs: submitting-patches: improve the base commit explanation

2023-11-15 Thread Konstantin Ryabitsev
On Wed, Nov 15, 2023 at 07:56:32PM +0200, Laurent Pinchart wrote: > When the base of a series is in Linus' tree, or in the corresponding > subsystem maintainer's tree, things are easy, but there are many > situations where the base is a merge of multiple branches (perhaps a > for-next and a fixes b

Re: [PATCH] docs: submitting-patches: improve the base commit explanation

2023-11-15 Thread Laurent Pinchart
On Wed, Nov 15, 2023 at 09:49:31AM -0800, Kees Cook wrote: > On Wed, Nov 15, 2023 at 06:03:30PM +0100, Borislav Petkov wrote: > > From: "Borislav Petkov (AMD)" > > > > After receiving a second patchset this week without knowing which tree > > it applies on and trying to apply it on the obvious on

Re: [PATCH] docs: submitting-patches: improve the base commit explanation

2023-11-15 Thread Kees Cook
On Wed, Nov 15, 2023 at 06:03:30PM +0100, Borislav Petkov wrote: > From: "Borislav Petkov (AMD)" > > After receiving a second patchset this week without knowing which tree > it applies on and trying to apply it on the obvious ones and failing, > make sure the base tree information which needs to

[PATCH] docs: submitting-patches: improve the base commit explanation

2023-11-15 Thread Borislav Petkov
From: "Borislav Petkov (AMD)" After receiving a second patchset this week without knowing which tree it applies on and trying to apply it on the obvious ones and failing, make sure the base tree information which needs to be supplied in the 0th message of the patchset is spelled out more explicit