From: Mark Brown <broonie@kernel.org>
To: Michal Simek <monstr@monstr.eu>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Grant Likely <grant.likely@linaro.org>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH 2/2] spi: convert drivers to use bits_per_word_mask
Date: Tue, 9 Jul 2013 22:49:10 +0100 [thread overview]
Message-ID: <20130709214910.GA3179@sirena.org.uk> (raw)
In-Reply-To: <51DC3078.5090602@monstr.eu>
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
On Tue, Jul 09, 2013 at 05:47:04PM +0200, Michal Simek wrote:
> Probably the best solution is just revert this part of patch.
> Mark: What do you think?
We should make it so that the user does not need to supply empty
functions if none are needed.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-09 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 2:36 [PATCH 1/2] spi: introduce macros to set bits_per_word_mask Stephen Warren
[not found] ` <1369190195-14598-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-22 2:36 ` [PATCH 2/2] spi: convert drivers to use bits_per_word_mask Stephen Warren
2013-05-24 17:16 ` H Hartley Sweeten
2013-05-29 19:49 ` Mark Brown
[not found] ` <1369190195-14598-2-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-31 8:45 ` Arnd Bergmann
2013-05-31 16:10 ` Stephen Warren
[not found] ` <51A8CB87.80201-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-31 21:23 ` Arnd Bergmann
2013-07-09 15:47 ` Michal Simek
2013-07-09 15:50 ` Stephen Warren
2013-07-09 21:49 ` Mark Brown [this message]
2013-07-09 21:56 ` Mark Brown
2013-05-22 15:58 ` [PATCH 1/2] spi: introduce macros to set bits_per_word_mask 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=20130709214910.GA3179@sirena.org.uk \
--to=broonie@kernel.org \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=swarren@wwwdotorg.org \
--cc=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).