From: Mark Brown <broonie@kernel.org>
To: Pelle Nilsson <per.nilsson@xelmo.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
nios2-dev@lists.rocketboards.org
Subject: Re: [PATCH 1/1] spi: altera: Add empty implementation of setup_transfer callback
Date: Thu, 9 Apr 2015 17:10:59 +0100 [thread overview]
Message-ID: <20150409161059.GA6023@sirena.org.uk> (raw)
In-Reply-To: <55269FDC.8040306@xelmo.com>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Thu, Apr 09, 2015 at 05:50:52PM +0200, Pelle Nilsson wrote:
> On 2015-04-09 17:40, Mark Brown wrote:
> > Why is the callback mandatory if an empty implementation is OK?
> Ask the author of spi-bitbang. :-)
What I'm trying to suggest is that you're perhaps fixing the wrong
problem - make the callback optional if there's a good reason for it.
Why is this patch the best fix?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-04-09 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 15:03 [PATCH 0/1] Fix NULL pointer dereference Pelle Nilsson
2015-04-09 15:03 ` [PATCH 1/1] spi: altera: Add empty implementation of setup_transfer callback Pelle Nilsson
2015-04-09 15:40 ` Mark Brown
2015-04-09 15:50 ` Pelle Nilsson
2015-04-09 16:10 ` Mark Brown [this message]
2015-04-13 9:45 ` Pelle Nilsson
2015-04-13 10:08 ` [PATCH] spi: bitbang: Make setup_transfer callback optional Pelle Nilsson
2015-04-14 0:22 ` [Nios2-dev] " Ezequiel Garcia
2015-04-14 13:40 ` [PATCH v2] spi: bitbang: Make setup_transfer() " Pelle Nilsson
2015-04-14 15:36 ` Ezequiel Garcia
2015-04-18 11:00 ` Mark Brown
2015-04-09 15:26 ` [PATCH 0/1] Fix NULL pointer dereference Mark Brown
2015-04-09 15:54 ` [PATCH v2] spi: altera: Add empty implementation of setup_transfer callback Pelle Nilsson
2015-04-09 16:23 ` 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=20150409161059.GA6023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nios2-dev@lists.rocketboards.org \
--cc=per.nilsson@xelmo.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
Powered by JetHome