From: Mark Brown <broonie@kernel.org>
To: Quentin Schulz <quentin.schulz@free-electrons.com>
Cc: nicolas.ferre@microchip.com, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org,
alexandre.belloni@free-electrons.com,
thomas.petazzoni@free-electrons.com
Subject: Re: [PATCH 1/2] spi: atmel: factorize reusable code for SPI controller init
Date: Fri, 14 Apr 2017 18:03:56 +0100 [thread overview]
Message-ID: <20170414170356.lbueenkw6lcv5vrp@sirena.org.uk> (raw)
In-Reply-To: <20170414082243.23002-1-quentin.schulz@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Fri, Apr 14, 2017 at 10:22:42AM +0200, Quentin Schulz wrote:
> The SPI controller configuration during the init can be reused, for the
> resume function for example.
Please don't resubmit patches that have already been applied, you should
submit patches against current code in the tree you're expecting things
to be applied to. If any updates are needed to a patch that's already
been applied you should submit incremental patches which make those
updates. This avoids having to change published git commits which could
cause problems for people working against git.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-04-14 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 8:22 [PATCH 1/2] spi: atmel: factorize reusable code for SPI controller init Quentin Schulz
2017-04-14 8:22 ` [PATCH 2/2] spi: atmel: add deepest PM support to SAMA5D2 Quentin Schulz
2017-04-14 10:35 ` Alexandre Belloni
2017-04-14 10:35 ` Alexandre Belloni
2017-04-18 8:50 ` Nicolas.Ferre
2017-04-14 10:35 ` [PATCH 1/2] spi: atmel: factorize reusable code for SPI controller init Alexandre Belloni
2017-04-14 10:35 ` Alexandre Belloni
2017-04-14 17:03 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-12 7:05 Quentin Schulz
2017-04-12 7:05 ` Quentin Schulz
2017-04-12 8:40 ` Nicolas Ferre
2017-04-12 8:40 ` Nicolas Ferre
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=20170414170356.lbueenkw6lcv5vrp@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=quentin.schulz@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.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 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.