From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: NeilBrown <neil@brown.name>
Cc: gregkh@linuxfoundation.org, driverdev-devel@linuxdriverproject.org
Subject: Re: [PATCH 5/5] staging: mt7621-gpio: remove device tree related stuff from TODO file
Date: Tue, 15 May 2018 06:55:20 +0200 [thread overview]
Message-ID: <20180515045520.GB17051@foobar> (raw)
In-Reply-To: <87h8n97lpt.fsf@notabene.neil.brown.name>
On Tue, May 15, 2018 at 11:26:38AM +1000, NeilBrown wrote:
> On Mon, May 14 2018, Sergio Paracuellos wrote:
>
> > Documentation related with device tree and its checkpatch complains
> > have been added. Update TODO file accordingly.
> >
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > ---
> > drivers/staging/mt7621-gpio/TODO | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/staging/mt7621-gpio/TODO b/drivers/staging/mt7621-gpio/TODO
> > index 7143905..492dbaa 100644
> > --- a/drivers/staging/mt7621-gpio/TODO
> > +++ b/drivers/staging/mt7621-gpio/TODO
> > @@ -1,5 +1,4 @@
> >
> > - general code review and clean up
> > -- ensure device-tree requirements are documented
> >
> > Cc: NeilBrown <neil@brown.name>
> > --
> > 2.7.4
>
> I said before that I could give a reviewed-by for this, but obviously I
> cannot as it depend on the bindings documentation which I didn't
> approve.
>
> However, it does look like I need to add things to the list.
> Apart from making sure interrupts work, the only thing I see in the code
> is various global variables (mediatek_gpio_membase, mediatek_gpio_irq,
> mediatek_gpio_irq_domain, gc_map) which should probably be in a
> drvdata allocated structure (stored with platform_set_drvdata() -
> plenty of examples in drivers/gpio/gpio-*.c)
> I think it would then be ready for submission to drivers/gpio
> and linux-gpio@vger.kernel.org.
Ack! I have just update TODO with this stuff in v2 series.
>
> Thanks,
> NeilBrown
Best regards,
Sergio Paracuellos
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-05-15 4:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 14:02 [PATCH 0/5] staging: mt7621-gpio: some driver cleanups Sergio Paracuellos
2018-05-14 14:02 ` [PATCH 1/5] staging: mt7621-gpio: fix some warnings because of lines exceded 80 characters Sergio Paracuellos
2018-05-14 14:02 ` [PATCH 2/5] staging: mt7621-gpio: add SPDX identifier Sergio Paracuellos
2018-05-14 14:02 ` [PATCH 3/5] dt-bindings: add compatible string for 'mtk' MediaTek Sergio Paracuellos
2018-05-15 7:24 ` Greg KH
2018-05-15 8:22 ` Sergio Paracuellos
2018-05-14 14:02 ` [PATCH 4/5] dt-bindings: gpio: add documentation for mt7621-gpio Sergio Paracuellos
2018-05-15 1:21 ` NeilBrown
2018-05-15 4:53 ` Sergio Paracuellos
2018-05-15 7:25 ` Greg KH
2018-05-15 8:22 ` Sergio Paracuellos
2018-05-14 14:02 ` [PATCH 5/5] staging: mt7621-gpio: remove device tree related stuff from TODO file Sergio Paracuellos
2018-05-15 1:26 ` NeilBrown
2018-05-15 4:55 ` Sergio Paracuellos [this message]
2018-05-15 1:01 ` [PATCH 0/5] staging: mt7621-gpio: some driver cleanups NeilBrown
2018-05-15 4:57 ` Sergio Paracuellos
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=20180515045520.GB17051@foobar \
--to=sergio.paracuellos@gmail.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=neil@brown.name \
/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.