linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <ardeleanalex@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Alexandru Ardelean <alexandru.ardelean@analog.com>,
	linux-iio <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Bastien Nocera <hadess@hadess.net>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH v2] iio: core: register chardev only if needed
Date: Sun, 13 Dec 2020 14:31:40 +0000	[thread overview]
Message-ID: <20201213143140.58af94a0@archlinux> (raw)
In-Reply-To: <CA+U=DspEg=XpOUKqtammKqOoLXoXEDKWQHqSauM1xna_Y+eqjA@mail.gmail.com>

On Wed, 9 Dec 2020 17:55:22 +0200
Alexandru Ardelean <ardeleanalex@gmail.com> wrote:

> On Wed, Dec 9, 2020 at 5:53 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> >
> > On Wed, Dec 9, 2020 at 5:45 PM Alexandru Ardelean
> > <ardeleanalex@gmail.com> wrote:  
> > > On Wed, Dec 9, 2020 at 5:37 PM Andy Shevchenko
> > > <andy.shevchenko@gmail.com> wrote:  
> > > > On Thu, Dec 3, 2020 at 11:55 AM Alexandru Ardelean
> > > > <alexandru.ardelean@analog.com> wrote:  
> >
> > ...
> >  
> > > > Are you sure there is no user space application that doesn't rely on
> > > > character device to be always present?  
> > >
> > > Nope.
> > > I'm not sure.
> > > I'm also not completely sure how Jonathan feels about this patch being
> > > added now [so late].
> > >
> > > Though, technically if the chardev was already there, without all the
> > > control in place [to enable IIO buffers and other stuff through the
> > > chardev] then it's technically just a "marker" file.
> > > Which arguably is a lot to have (i.e. chardev that should be unusable).
> > >
> > > If it is usable with no control in place for buffers or other stuff
> > > (i.e. I missed something), then I also don't know.
> > >
> > > So, this patch on it's own can still be interpreted as an RFC.
> > > See:
> > > https://lore.kernel.org/linux-iio/20201121180246.772ad299@archlinux/  
> >
> > Don't take me wrong, I'm not against a good change (I doesn't like
> > dangling files), but it might break some use cases.  
> 
> Yeah I know.
> But how else do you know if a dangling file might break some use cases?
> 
> The worst that would happen is that we get a report and create a Fixes
> tag and we know.
> But if we don't try it, we're stuck with it, and will never know.
> 
It's definitely a high risk change.  I'd 'hope' it's not a problem
but we should do a bit more due diligence. 

I hope we can assume the ADI software is all fine with dropping this.
Bastien can you see any issues with dropping chrdev for IIO devices
that don't actually support using it for anything (sysfs interface only).

What other stacks are people aware of that we should enquire about?

Thanks,

Jonathan
> >
> > --
> > With Best Regards,
> > Andy Shevchenko  


  reply	other threads:[~2020-12-13 14:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03  9:53 [PATCH v2] iio: core: register chardev only if needed Alexandru Ardelean
2020-12-09 15:19 ` Andy Shevchenko
2020-12-09 15:45   ` Alexandru Ardelean
2020-12-09 15:54     ` Andy Shevchenko
2020-12-09 15:55       ` Alexandru Ardelean
2020-12-13 14:31         ` Jonathan Cameron [this message]
2021-01-19  8:18           ` Alexandru Ardelean
  -- strict thread matches above, loose matches on Subject: below --
2020-04-14  8:36 Alexandru Ardelean
2020-04-14 18:06 ` Jonathan Cameron
2020-04-15 13:56   ` Ardelean, Alexandru
2020-04-15 14:55     ` Lars-Peter Clausen
2020-04-16  7:04       ` Ardelean, Alexandru

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=20201213143140.58af94a0@archlinux \
    --to=jic23@kernel.org \
    --cc=alexandru.ardelean@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=ardeleanalex@gmail.com \
    --cc=hadess@hadess.net \
    --cc=hdegoede@redhat.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.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).