From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Shravan.Chippa@microchip.com, paul.j.murphy@intel.com,
daniele.alessandrelli@intel.com, mchehab@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, festevam@gmail.com,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
sakari.ailus@iki.fi
Subject: Re: [PATCH RESEND v10 4/5] dt-bindings: media: i2c: imx334 add new link_freq
Date: Mon, 23 Jan 2023 16:48:09 -0600 [thread overview]
Message-ID: <20230123224809.GA2738495-robh@kernel.org> (raw)
In-Reply-To: <be218243-a2e7-d9d0-bd7f-ba3c18846f75@linaro.org>
On Mon, Jan 23, 2023 at 09:00:30AM +0100, Krzysztof Kozlowski wrote:
> On 23/01/2023 07:28, Shravan.Chippa@microchip.com wrote:
> > Hi,
> >
> >> -----Original Message-----
> >> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >> Sent: 22 January 2023 07:37 PM
> >> To: shravan Chippa - I35088 <Shravan.Chippa@microchip.com>;
> >> paul.j.murphy@intel.com; daniele.alessandrelli@intel.com;
> >> mchehab@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> >> shawnguo@kernel.org; s.hauer@pengutronix.de
> >> Cc: festevam@gmail.com; kernel@pengutronix.de; linux-imx@nxp.com;
> >> linux-media@vger.kernel.org; linux-kernel@vger.kernel.org;
> >> devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; Sakari
> >> Ailus <sakari.ailus@iki.fi>
> >> Subject: Re: [PATCH RESEND v10 4/5] dt-bindings: media: i2c: imx334 add
> >> new link_freq
> >>
> >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> >> content is safe
> >>
> >> On 21/01/2023 04:37, shravan kumar wrote:
> >>> From: Shravan Chippa <shravan.chippa@microchip.com>
> >>>
> >>> Add new supported link frequency in dt example.
> >>
> >> You got a comment to fix you CC list. Why not follow my feedback?
> >
> > Based on your previous comment I ran the below script, rebased to the latest code and based on that output I have added a CC list
> > But I missed adding one name to the to-list which is "Rob Herring <robh+dt@kernel.org>", I will add it.
>
> Which is quite important...
Not really. I've long since given up trying to filter based on that. The
DT list vs. to me is about the same firehose. Expecting senders to get
it right or figure out what's important to you or not will never happen.
With lore now, there's little need as I control what I get or not.
Rob
next prev parent reply other threads:[~2023-01-23 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 3:37 [PATCH RESEND v10 0/5] media: i2c: imx334: support lower bandwidth mode shravan kumar
2023-01-21 3:37 ` [PATCH RESEND v10 1/5] media: i2c: imx334: replace __v4l2_ctrl_s_ctrl to __v4l2_ctrl_modify_range shravan kumar
2023-01-21 3:37 ` [PATCH RESEND v10 2/5] media: i2c: imx334: add missing reset values for mode 3840x2160_regs[] shravan kumar
2023-01-21 3:37 ` [PATCH RESEND v10 3/5] media: i2c: imx334: support lower bandwidth mode shravan kumar
2023-01-21 3:37 ` [PATCH RESEND v10 4/5] dt-bindings: media: i2c: imx334 add new link_freq shravan kumar
2023-01-22 14:07 ` Krzysztof Kozlowski
2023-01-23 6:28 ` Shravan.Chippa
2023-01-23 8:00 ` Krzysztof Kozlowski
2023-01-23 22:48 ` Rob Herring [this message]
2023-01-21 3:37 ` [PATCH RESEND v10 5/5] media: i2c: imx334: update pixel and link frequency shravan kumar
2023-01-23 23:02 ` Sakari Ailus
2023-01-24 5:34 ` Shravan.Chippa
2023-01-25 9:42 ` Sakari Ailus
2023-01-27 0:10 ` Shravan.Chippa
2023-02-06 4:43 ` Shravan.Chippa
2023-02-22 9:16 ` Sakari Ailus
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=20230123224809.GA2738495-robh@kernel.org \
--to=robh@kernel.org \
--cc=Shravan.Chippa@microchip.com \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.j.murphy@intel.com \
--cc=s.hauer@pengutronix.de \
--cc=sakari.ailus@iki.fi \
--cc=shawnguo@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).