[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <61fdb731-1ebb-941c-4bd7-7da8c31c8e74@ideasonboard.com>
Date: Wed, 30 Mar 2022 13:50:35 +0300
From: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
To: Sakari Ailus <sakari.ailus@...ux.intel.com>,
Tom Rix <trix@...hat.com>
Cc: mchehab@...nel.org, gregkh@...uxfoundation.org, nathan@...nel.org,
ndesaulniers@...gle.com, hverkuil-cisco@...all.nl, vrzh@...h.net,
linux-media@...r.kernel.org, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH] media: staging: atomisp: rework reading the id and
revision values
On 30/03/2022 13:33, Sakari Ailus wrote:
> Hi Tom,
>
> On Tue, Mar 29, 2022 at 04:21:20PM -0700, Tom Rix wrote:
>> I'll do a resend.
>>
>> I use git send-mail, sooo not sure what went wrong.
>
> The resent patch also has the same Content-type. I looked a bit further and
> it seems that this is very probably added by our mail system somehow: it's
> not present on the patch I received through a different route. Weird.
Well... For me, the original patch in this thread was text/plain. But
the [RESEND PATCH] was application/octet-stream, and Thunderbird shows
it as empty body with an unnamed attachment.
Tomi
Powered by blists - more mailing lists