All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Jan Kundrát" <jan.kundrat@cesnet.cz>
Cc: Lukasz Majewski <lukma@denx.de>, 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: Mon, 1 Oct 2018 15:22:19 +0100	[thread overview]
Message-ID: <20181001142219.GB19099@sirena.org.uk> (raw)
In-Reply-To: <47e37a54-6df6-47c0-b38b-ad35e9bd4ce4@cesnet.cz>

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

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.  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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-10-01 14:22 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 [this message]
2018-10-02  8:11     ` Lukasz Majewski
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
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=20181001142219.GB19099@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.