From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/7] mailbox: arm_mhu: add driver for ARM MHU controller
Date: Thu, 5 Feb 2015 12:08:29 +0000 [thread overview]
Message-ID: <20150205120829.GO8656@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAJe_Zhf_WuRK2EE0Sj9ksXDDe5VA=DJ+H3eS4YRKpDZLdRRfow@mail.gmail.com>
On Thu, Feb 05, 2015 at 05:32:39PM +0530, Jassi Brar wrote:
> On Feb 5, 2015 5:13 PM, "Arnd Bergmann" <arnd@arndb.de> wrote:
> >
> > >
> > > I know typedef's are frowned upon, but how bad is the following option?
> > > typedef void* mbox_data_info
> > > int mbox_send_message(struct mbox_chan *chan, mbox_data_info
> data);
> >
> > I don't see how that would help.
> >
> If it's abuse because the argument is a void*... What if we called it
> mbox_data_info? To say platforms are free to pass data as a pointer or a
> value :)
Using a typedef really doesn't change anything. If you read the kernel
coding style, you'll realise that typedefs are a reason to reject
patches - especially to use them in the way you are proposing.
Try the solution I suggested (which I notice was seemingly totally
ignored.)
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-02-05 12:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 9:21 [PATCH v5 0/7] Support for Fujitsu MB86S7X SoCs Vincent Yang
2015-02-03 9:27 ` [PATCH v5 1/7] ARM: Add platform support " Vincent Yang
2015-02-03 9:29 ` [PATCH v5 2/7] mailbox: arm_mhu: add driver for ARM MHU controller Vincent Yang
2015-02-03 12:32 ` Russell King - ARM Linux
2015-02-03 14:39 ` Jassi Brar
2015-02-03 14:46 ` Russell King - ARM Linux
2015-02-03 15:25 ` Arnd Bergmann
2015-02-04 3:27 ` Jassi Brar
2015-02-04 10:29 ` Arnd Bergmann
2015-02-04 14:34 ` Jassi Brar
2015-02-04 14:48 ` Arnd Bergmann
2015-02-04 15:33 ` Jassi Brar
2015-02-04 16:42 ` Arnd Bergmann
2015-02-05 5:08 ` Jassi Brar
2015-02-05 11:43 ` Arnd Bergmann
[not found] ` <CAJe_Zhf_WuRK2EE0Sj9ksXDDe5VA=DJ+H3eS4YRKpDZLdRRfow@mail.gmail.com>
2015-02-05 12:08 ` Russell King - ARM Linux [this message]
2015-02-05 12:31 ` Arnd Bergmann
2015-02-05 14:50 ` Jassi Brar
2015-02-04 15:09 ` Russell King - ARM Linux
2015-02-03 9:30 ` [PATCH v5 3/7] ARM: MB86S7X: Add MCPM support Vincent Yang
2015-02-03 9:31 ` [PATCH v5 4/7] clk: Add clock driver for mb86s7x Vincent Yang
2015-02-03 9:32 ` [PATCH v5 5/7] dt: mb86s7x: add dt files for MB86S7x evbs Vincent Yang
2015-02-03 9:34 ` [PATCH v5 6/7] of: add Fujitsu vendor prefix Vincent Yang
2015-02-03 9:35 ` [PATCH v5 7/7] ARM: MB86S7x: Add configs Vincent Yang
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=20150205120829.GO8656@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).