[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAtXAHekFyL=N96vZYp9rUJMUcBW31Jj=+7J1=aiGpH4Gg1OxQ@mail.gmail.com>
Date: Wed, 18 Nov 2015 20:50:35 -0800
From: Moritz Fischer <moritz.fischer@...us.com>
To: Alan Tull <atull@...nsource.altera.com>
Cc: Rob Herring <robh+dt@...nel.org>, Josh Cartwright <joshc@...com>,
Greg KH <gregkh@...uxfoundation.org>,
Michal Simek <monstr@...str.eu>,
Michal Simek <michal.simek@...inx.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Alan Tull <delicious.quinoa@...il.com>,
"dinguyen@...nsource.altera.com" <dinguyen@...nsource.altera.com>
Subject: Re: [PATCH v13 4/6] fpga: add fpga bridge framework
Hi Alan,
while trying to implement something that works for Zynq along these lines
I stumbled upon some minor stuff.
On Tue, Nov 3, 2015 at 9:11 AM, <atull@...nsource.altera.com> wrote:
> + * Return: 0 on success, negative error code otherwise.
> + */
> +int fpga_bridge_register(struct device *dev, const char *name,
> + struct fpga_bridge_ops *br_ops, void *priv)
const struct fpga_bridge_ops
> +int fpga_bridge_register(struct device *dev, const char *name,
> + struct fpga_bridge_ops *br_ops, void *priv);
const struct fpga_bridge_ops
Cheers,
Moritz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists