On Thu, May 15, 2025 at 09:33:18PM +0200, Simon Glass wrote: > Hi Tom, > > On Thu, 15 May 2025 at 15:55, Tom Rini <tr...@konsulko.com> wrote: > > > > On Thu, May 15, 2025 at 06:51:17AM -0700, Simon Glass wrote: > > > This function is useful for other scripts, so add a parameter to specify > > > the image name, if desired. > > > > > > Also add a flag to quieten the output of some of the tools, since in > > > many cases we only want to see warnings / errors. > > > > > > Signed-off-by: Simon Glass <s...@chromium.org> > > > --- > > > > > > test/py/tests/fs_helper.py | 18 +++++++++++++----- > > > 1 file changed, 13 insertions(+), 5 deletions(-) > > > > > > Applied to sjg/master, thanks! > > > > You have been repeatedly asked to not send messages about your personal > > tree to the list. Please stop sending these messages (and I hope you > > didn't change the patchwork status too, again). > > We are still not really on the same page here.
Yes, you keep not following seemingly clear directions. You posted something not against master, and that also continued adding things which do not belong in the tree, to the tree. > This series is showing as rejected in patchwork, so I've applied it to > my tree and sent an appropriate message There is no appropriate message to send to the public mailing list for your downstream tree, stop doing that. And patchwork reflects mainline, not your personal tree. > While we are in this state of > your rejecting my patches, I am not sure what else I can do. I have > already renamed the tree, as you requested, so there should be no > confusion that this is my tree. If there is still confusion, then > perhaps the rename (which took quite a bit of effort) was not > effective in resolving your concerns? Your downstream tree is not a special tree. Others have explained how they maintain downstream trees and work on upstreaming changes. > If you do take a pull request (e.g. for one of the 100+ patches > assigned to me in patchwork right now), the patches will then be in > your tree, so presumably need to be marked 'accepted' in patchwork. > When would be the best time for me to change this status? The status of patches for mainline in patchwork is pretty easy. I even run some helper scripts every tag to update (most) patches that might have been missed. > BTW, I'm really not sure why you have rejected this particular patch. > Even if you don't want scripts maintained in your tree, this is really > just a small tweak. It will help reduce the delta between our trees. It was rejected either because it wasn't against mainline, or because it contained changes that had already been rejected. -- Tom
signature.asc
Description: PGP signature