Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 30 Aug 2022 08:22:17 -0400
From:   Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To:     Maxime Ripard <maxime@cerno.tech>
Cc:     linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 01/41] drm/tests: Order Kunit tests in Makefile
Message-ID: <20220830122217.h52zswusnlb3iggq@meerkat.local>
References: <20220728-rpi-analog-tv-properties-v2-0-459522d653a7@cerno.tech>
 <20220728-rpi-analog-tv-properties-v2-1-459522d653a7@cerno.tech>
 <f6289e5d-98e3-1a0d-f514-136e2b7978c1@tronnes.org>
 <20220829190242.tk2hinttzzmzhnaj@meerkat.local>
 <20220830083027.4iyi2s5r5bto4h2e@houat>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20220830083027.4iyi2s5r5bto4h2e@houat>
Precedence: bulk

(Dropping most cc's, who probably don't care about this thread.)

On Tue, Aug 30, 2022 at 10:30:27AM +0200, Maxime Ripard wrote:
> > I noticed this, too, and I think the reason is because these patches were
> > generated with "b4 send -o", but actually sent using git-send-email. It's not
> > a use-case I've considered (or tested) and the breakage is because when b4
> > generates patches with "-o", they are written with CRLF line endings, which is
> > not something git-send-email expects.
> 
> You're right

OK, the latest master should allow you to do that without causing CRLF errors
like this series.

> For some reason, b4 send doesn't work for my setup and I haven't had the
> time to look into why and let you know.

Yeah, I see what the cause of it is:

> Connecting to /home/max/.local/bin/msmtpq:0
> Failed to configure the smtp connection:
> [Errno -2] Name or service not known

You have sendemail.smtpserver set to a path, which is supported by
git-sendemail, but not by b4 (yet). I'll see if I can put that in today.

Thank you for testing out b4 send!

-K