From: Linus Walleij <linus.walleij@linaro.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Subject: Re: [PATCH v1 2/5] gpio: stmpe: Remove unused 'dev' member of struct stmpe_gpio
Date: Thu, 5 Sep 2024 13:34:18 +0200 [thread overview]
Message-ID: <CACRpkdZ15jP429o2STJrjArsDRbr=sE27DnwFucpvz-ksEsReg@mail.gmail.com> (raw)
In-Reply-To: <20240902133148.2569486-3-andriy.shevchenko@linux.intel.com>
On Mon, Sep 2, 2024 at 3:32 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
> There is no evidence that the 'dev' member of struct stmpe_gpio
> is used, drop it.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2024-09-05 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 13:30 [PATCH v1 0/5] gpio: stmpe: A few cleanups Andy Shevchenko
2024-09-02 13:30 ` [PATCH v1 1/5] gpio: stmpe: Fix IRQ related error messages Andy Shevchenko
2024-09-05 11:33 ` Linus Walleij
2024-09-02 13:30 ` [PATCH v1 2/5] gpio: stmpe: Remove unused 'dev' member of struct stmpe_gpio Andy Shevchenko
2024-09-05 11:34 ` Linus Walleij [this message]
2024-09-02 13:30 ` [PATCH v1 3/5] gpio: stmpe: Utilise temporary variable for struct device Andy Shevchenko
2024-09-05 11:35 ` Linus Walleij
2024-09-02 13:30 ` [PATCH v1 4/5] gpio: stmpe: Make use of device properties Andy Shevchenko
2024-09-05 11:35 ` Linus Walleij
2024-09-02 13:30 ` [PATCH v1 5/5] gpio: stmpe: Sort headers Andy Shevchenko
2024-09-05 11:35 ` Linus Walleij
2024-09-04 7:03 ` [PATCH v1 0/5] gpio: stmpe: A few cleanups Bartosz Golaszewski
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='CACRpkdZ15jP429o2STJrjArsDRbr=sE27DnwFucpvz-ksEsReg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@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 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).