From: Mark Brown <broonie@kernel.org>
To: Lukasz Majewski <lukma@denx.de>
Cc: "Jan Kundrát" <jan.kundrat@cesnet.cz>,
"Shawn Guo" <shawnguo@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spidev: Enable the Liebherr's BK4 board to work with spidev driver
Date: Tue, 2 Oct 2018 14:09:50 +0100 [thread overview]
Message-ID: <20181002130950.GB6338@sirena.org.uk> (raw)
In-Reply-To: <20181002101120.0f92f296@jawa>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
On Tue, Oct 02, 2018 at 10:11:20AM +0200, Lukasz Majewski wrote:
> > As documented in SubmittingPatches please send patches to the
> > maintainers for the code you would like to change.
> I'm using the ./scripts/get_maintainer.py script to obtain list of
> relevant people.
Your patch went to the right place (and I applied it yesterday), that
was directed at Jan - the reason his patch got missed is that he didn't
send it to me.
> Please also document in the ./Documentation/devicetree the introduced
> compatible -> there are some examples (ge,ahca) in the misc directory.
Good point.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-02 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 22:31 [PATCH] spidev: Enable the Liebherr's BK4 board to work with spidev driver Lukasz Majewski
2018-10-01 14:20 ` Jan Kundrát
2018-10-01 14:22 ` Mark Brown
2018-10-02 8:11 ` Lukasz Majewski
2018-10-02 13:09 ` Mark Brown [this message]
2018-10-08 13:57 ` Applied "spidev: Enable the Liebherr's BK4 board to work with spidev driver" to the spi tree Mark Brown
2018-10-08 13:57 ` Mark Brown
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=20181002130950.GB6338@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jan.kundrat@cesnet.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukma@denx.de \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
/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.