From: Lukasz Majewski <lukma@denx.de>
To: Mark Brown <broonie@kernel.org>
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 10:11:20 +0200 [thread overview]
Message-ID: <20181002101120.0f92f296@jawa> (raw)
In-Reply-To: <20181001142219.GB19099@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
Hi Jan,
> On Mon, Oct 01, 2018 at 04:20:32PM +0200, Jan Kundrát wrote:
>
> > Hi Lukasz,
> > I tried submitting a similar patch for another devicem but got no
> > reaction [1]. In the meanwhile, there has been another proposal [2]
> > which moves
>
> 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.
Moreover, you may want to look for gitk -- <patch to your modified
file> and add developers, who did some remarkable work in that file.
Also git-blame helps.
And another issue - maitainers are very often very busy (as
maintaining/reviewing is not their main occupation).
We would like to have a prompt response/review, but it is acceptable to
wait week or two for reply....
Please also document in the ./Documentation/devicetree the introduced
compatible -> there are some examples (ge,ahca) in the misc directory.
> The normal kernel
> workflow is that people apply patches from their inboxes, if they
> aren't copied they are likely to not see the patch at all and it is
> much more difficult to apply patches.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-02 8:11 UTC|newest]
Thread overview: 6+ 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 [this message]
2018-10-02 13:09 ` Mark Brown
2018-10-08 13:57 ` Applied "spidev: Enable the Liebherr's BK4 board to work with spidev driver" to the spi tree 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=20181002101120.0f92f296@jawa \
--to=lukma@denx.de \
--cc=broonie@kernel.org \
--cc=jan.kundrat@cesnet.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox