From: Jonathan Cameron <jic23@kernel.org>
To: Subhajit Ghosh <subhajit.ghosh@tweaklogic.com>
Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Shreeya Patel <shreeya.patel@collabora.com>,
Paul Gazzillo <paul@pgazz.com>,
Zhigang Shi <Zhigang.Shi@liteon.com>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>
Subject: Re: [RFC PATCH 0/2] Support for Avago APDS9306 Ambient Light Sensor
Date: Wed, 12 Apr 2023 21:44:03 +0100 [thread overview]
Message-ID: <20230412214403.5c053ed6@jic23-huawei> (raw)
In-Reply-To: <eefdbad5-35ed-04c6-0955-87c99a4d345d@tweaklogic.com>
On Wed, 12 Apr 2023 12:46:49 +0800
Subhajit Ghosh <subhajit.ghosh@tweaklogic.com> wrote:
> Hi Jonathan,
> Thank you for getting back.
>
> > Hi Subhajit,
> >
> > No need to sign off a cover letter. The content isn't captured in the
> > git tree anyway.
> >
> > For an RFC, I'd expect to see a clear statement in the cover letter of
> > why it is an RFC rather than a formal patch submission. What specifically
> > are you looking for comments on?
> >
> > Point us in the right direction and we might answer the questions quicker.
> >
> > Thanks,
> >
> > Jonathan
> Thank you for clearing it up.
> Next version of RFC I will put specific reasons.
> Before submitting a formal patch I wanted to check if my implementation of
> single reads of ALS data raw values from userspace when interrupts are
> enabled is the right thing to do or not. Also wanted to check if my event
> related userspace ABI implementation is in line with IIO subsystem.
> I will put it into better words in the next cover letter.
>
> Can you also help me out with the git tree I should use to format the
> patches? As per my understanding it is the subsystem maintainer tree
> and the main branch but the macros and functions which you have suggested
> in other reviews are available in Linux mainline.
For a new driver it rarely matters and I'd advise simply using
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
which is the mainline tree. Please base either on the previous
release (currently 6.2) or rc1 of the current release (v6.3-rc1)
if doing this.
If you need a feature that has only been applied in the same cycle, or
are building on recent work that has been applied to the iio tree then
for fixes you want:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git fixes-togreg
for new stuff you want:
https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
The IIO tree routes through Greg KH's char-misc tree so will see the togreg
branch move forwards to be based on that as Greg takes pull requests from me.
Usually this happens once or twice a kernel cycle. Don't worry too much about
this. If it should affect a patch because some changes crossed I'll generally
fix it up whilst applying whichever gets applied second and ask the
authors to check I didn't make a mistake.
Joanthan
>
> Regards,
> Subhajit Ghosh
>
next prev parent reply other threads:[~2023-04-12 20:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 1:12 [RFC PATCH 0/2] Support for Avago APDS9306 Ambient Light Sensor Subhajit Ghosh
2023-04-11 1:12 ` [RFC PATCH 1/2] dt-bindings: Document APDS9306 Light Sensor bindings Subhajit Ghosh
2023-04-11 12:27 ` Rob Herring
2023-04-12 1:13 ` Subhajit Ghosh
2023-04-12 7:12 ` Krzysztof Kozlowski
2023-04-12 8:14 ` Subhajit Ghosh
2023-04-11 1:12 ` [RFC PATCH 2/2] iio: light: Add support for APDS9306 Light Sensor Subhajit Ghosh
2023-04-11 12:43 ` Andy Shevchenko
2023-04-12 4:29 ` Subhajit Ghosh
2023-04-12 13:37 ` Andy Shevchenko
2023-04-13 3:33 ` Subhajit Ghosh
2023-04-15 17:35 ` Jonathan Cameron
2023-04-17 9:25 ` Subhajit Ghosh
2023-04-23 11:36 ` Jonathan Cameron
2023-04-11 13:40 ` [RFC PATCH 0/2] Support for Avago APDS9306 Ambient " Jonathan Cameron
2023-04-12 4:46 ` Subhajit Ghosh
2023-04-12 20:44 ` Jonathan Cameron [this message]
2023-04-13 3:14 ` Subhajit Ghosh
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=20230412214403.5c053ed6@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=Zhigang.Shi@liteon.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@pgazz.com \
--cc=robh+dt@kernel.org \
--cc=shreeya.patel@collabora.com \
--cc=subhajit.ghosh@tweaklogic.com \
/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