From: Andrew Lunn <andrew@lunn.ch>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Woojung.Huh@microchip.com, UNGLinuxDriver@microchip.com,
vivien.didelot@savoirfairelinux.com,
Florian Fainelli <f.fainelli@gmail.com>,
driverdev-devel@linuxdriverproject.org, netdev@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: net: dsa: ksz9477: fix indentation for switch spi bindings
Date: Tue, 25 Dec 2018 13:38:54 +0100 [thread overview]
Message-ID: <20181225123854.GA27955@lunn.ch> (raw)
In-Reply-To: <CAMhs-H9o6z6YcnVTwHEnbr4vknEnHbSFvoobbscsx3isG5+G4A@mail.gmail.com>
On Tue, Dec 25, 2018 at 12:45:11PM +0100, Sergio Paracuellos wrote:
> Hi David,
>
> On Mon, Dec 24, 2018 at 11:15 PM David Miller <davem@davemloft.net> wrote:
> >
> > From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > Date: Sat, 22 Dec 2018 08:39:09 +0100
> >
> > > Switch bindings for spi managed mode are using spaces instead of tabs.
> > > Fix them to get a file with a proper kernel indentation style.
> > >
> > > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> >
> > This doesn't apply to any of my trees so I'm going to assume this was
> > targetting the devicetree GIT tree or something like that.
>
> Actually, this was rebased onto linux-next. Which tree do you want me
> to rebase onto?
Hi Sergio
It should be based on net-next. However, that is closed now, so please
wait until it reopens in about two weeks time.
Thanks
Andrew
next prev parent reply other threads:[~2018-12-25 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 7:39 [PATCH] dt-bindings: net: dsa: ksz9477: fix indentation for switch spi bindings Sergio Paracuellos
2018-12-23 22:16 ` Florian Fainelli
2018-12-24 22:15 ` David Miller
2018-12-25 11:45 ` Sergio Paracuellos
2018-12-25 12:38 ` Andrew Lunn [this message]
2018-12-25 18:41 ` 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=20181225123854.GA27955@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=vivien.didelot@savoirfairelinux.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).