From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Tom Rix <trix@redhat.com>
Cc: mchehab@kernel.org, gregkh@linuxfoundation.org,
nathan@kernel.org, ndesaulniers@google.com,
hverkuil-cisco@xs4all.nl, vrzh@vrzh.net,
tomi.valkeinen@ideasonboard.com, linux-media@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] media: staging: atomisp: rework reading the id and revision values
Date: Wed, 30 Mar 2022 13:33:14 +0300 [thread overview]
Message-ID: <YkQx6jk5V2/f5mye@paasikivi.fi.intel.com> (raw)
In-Reply-To: <2ab474d8-ee4e-44b5-ab3c-38b72135a27f@redhat.com>
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
next prev parent reply other threads:[~2022-03-30 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 19:18 trix
2022-03-29 21:06 ` Sakari Ailus
2022-03-29 23:21 ` Tom Rix
2022-03-30 10:33 ` Sakari Ailus [this message]
2022-03-30 10:50 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YkQx6jk5V2/f5mye@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=llvm@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=trix@redhat.com \
--cc=vrzh@vrzh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®