From: Greg KH <gregkh@linuxfoundation.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-staging@lists.linux.dev, NeilBrown <neil@brown.name>
Subject: Re: [PATCH 1/2] staging: mt7621-dts: get rid of nodes with no in-tree driver
Date: Mon, 18 Oct 2021 17:33:39 +0200 [thread overview]
Message-ID: <YW2T06FWg2pGreOL@kroah.com> (raw)
In-Reply-To: <CAMhs-H_BKw8e6hObS3Tx-iO44xbyZh2Q+=jVtxykJ=6hx1Rheg@mail.gmail.com>
On Mon, Oct 18, 2021 at 05:29:16PM +0200, Sergio Paracuellos wrote:
> Hi Greg,
>
> On Sun, Oct 17, 2021 at 9:06 AM Sergio Paracuellos
> <sergio.paracuellos@gmail.com> wrote:
> >
> > Nodes for 'i2s' and 'nand' have no driver present inside the linux tree.
> > The normal approach for a dts file to be mainlined is start with those stuff
> > which is already mainlined and get rid of the other stuff. If needed it will
> > be properly added afterwards together with the suitable device driver. Hence,
> > remove both nodes from the device tree include file.
> >
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > ---
> > drivers/staging/mt7621-dts/mt7621.dtsi | 36 --------------------------
> > 1 file changed, 36 deletions(-)
>
> I noticed PATCH 2/2 of this series was added but not this one which is
> the first one in the series. Since I did not see any mail or something
> complaining about it... is it possible you missed it?
It did not apply to my tree as it seems to already be there. Try
rebasing and resending if it really is not.
thanks,
greg k-h
next prev parent reply other threads:[~2021-10-18 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 7:06 [PATCH 1/2] staging: mt7621-dts: get rid of nodes with no in-tree driver Sergio Paracuellos
2021-10-17 7:06 ` [PATCH 2/2] staging: mt7621-dts: change some node hex addresses to lower case Sergio Paracuellos
2021-10-18 15:29 ` [PATCH 1/2] staging: mt7621-dts: get rid of nodes with no in-tree driver Sergio Paracuellos
2021-10-18 15:33 ` Greg KH [this message]
2021-10-18 15:37 ` 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=YW2T06FWg2pGreOL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-staging@lists.linux.dev \
--cc=neil@brown.name \
--cc=sergio.paracuellos@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