From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: JaimeLiao <jaimeliao.tw@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [PATCH v1 1/1] mtd: rawnand: Remove unused of_gpio.h inclusion
Date: Fri, 6 Oct 2023 17:41:37 +0200 [thread overview]
Message-ID: <20231006174137.2e745cb4@xps-13> (raw)
In-Reply-To: <ZSAkUMnXw4SbS2pC@smile.fi.intel.com>
Hi Andy,
andriy.shevchenko@linux.intel.com wrote on Fri, 6 Oct 2023 18:14:24
+0300:
> +Cc: GPIO maintainers
>
> On Mon, Jul 10, 2023 at 01:00:51PM +0300, Andy Shevchenko wrote:
> > On Fri, Jun 16, 2023 at 12:10:52AM +0200, Martin Blumenstingl wrote:
> > > On Thu, Jun 15, 2023 at 6:42 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > The of_gpio.h is not and shouldn't be used in the drivers. Remove it.
> > > >
> > > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> >
> > Thank you!
> >
> > Can it be applied now?
>
> So, this is still not applied, does it mean we need to go via GPIO tree
> with it?
I remember your ping and also answering it, but I cannot find it. Let
me look into this. In any case, apologies for that.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-10-06 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 16:42 [PATCH v1 1/1] mtd: rawnand: Remove unused of_gpio.h inclusion Andy Shevchenko
2023-06-15 22:10 ` Martin Blumenstingl
2023-07-10 10:00 ` Andy Shevchenko
2023-10-06 15:14 ` Andy Shevchenko
2023-10-06 15:41 ` Miquel Raynal [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=20231006174137.2e745cb4@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jaimeliao.tw@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vigneshr@ti.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