From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Kent Gibson <warthog618@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH 0/5] core: provide information about the parent chip in line requests
Date: Thu, 20 Jul 2023 11:42:41 +0300 [thread overview]
Message-ID: <ZLjzgYzUG8dhKnyH@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=Mf=Xf7KPP+9GPC6=1Gsp3XTfzrwjOK2jrqeP7QUVxtD+Q@mail.gmail.com>
On Thu, Jul 20, 2023 at 09:59:00AM +0200, Bartosz Golaszewski wrote:
> On Thu, Jul 20, 2023 at 5:27 AM Kent Gibson <warthog618@gmail.com> wrote:
...
> as it would be the one allowing the caller to reopen the same chip.
Since you do not control the lifetime of the files, the above may not be
guaranteed. So, this path is just an arbitrary information from the past.
It _was_ consistent with the request, but it does _not_ mean it still is.
I would rely on the chip name, which is provided by the DT/driver, if
possible.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-07-20 8:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 19:20 [libgpiod][PATCH 0/5] core: provide information about the parent chip in line requests Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 1/5] core: provide gpiod_line_request_get_chip_path() Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 2/5] tests: add a test-case for gpiod_line_request_get_chip_path() Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 3/5] bindings: cxx: provide line_request::chip_path() Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 4/5] bindings: python: provide the chip_path property in line_request Bartosz Golaszewski
2023-07-19 19:20 ` [libgpiod][PATCH 5/5] bindings: rust: provide LineRequest::chip_path() Bartosz Golaszewski
2023-07-20 5:04 ` Erik Schilling
2023-07-20 8:04 ` Bartosz Golaszewski
2023-07-20 8:10 ` Erik Schilling
2023-07-20 3:27 ` [libgpiod][PATCH 0/5] core: provide information about the parent chip in line requests Kent Gibson
2023-07-20 7:59 ` Bartosz Golaszewski
2023-07-20 8:05 ` Kent Gibson
2023-07-20 8:25 ` Bartosz Golaszewski
2023-07-20 8:39 ` Kent Gibson
2023-07-20 8:49 ` Bartosz Golaszewski
2023-07-20 9:16 ` Kent Gibson
2023-07-20 9:38 ` Bartosz Golaszewski
2023-07-20 9:52 ` Kent Gibson
2023-07-20 12:30 ` Bartosz Golaszewski
2023-07-20 13:37 ` Kent Gibson
2023-07-20 15:01 ` Bartosz Golaszewski
2023-07-21 1:37 ` Kent Gibson
2023-07-20 8:42 ` Andy Shevchenko [this message]
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=ZLjzgYzUG8dhKnyH@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.