[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkQx6jk5V2/f5mye@paasikivi.fi.intel.com>
Date: Wed, 30 Mar 2022 13:33:14 +0300
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: 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,
tomi.valkeinen@...asonboard.com, 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
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.
git format-patch only seems to add the header sometimes based on some
obscure criteria. It's the first time I see such a problem. It'd at least
help if the Content-type would always be there but that's certainly out of
scope of the patch.
--
Regards,
Sakari Ailus
Powered by blists - more mailing lists