From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiner Kallweit Subject: Re: [PATCH 1/3] spi: core: add max_msg_size to spi_master Date: Mon, 30 Nov 2015 21:15:43 +0100 Message-ID: <565CAE6F.3070002@gmail.com> References: <20151120120502.GT31303@sirena.org.uk> <08871ECD-52DF-4CBF-AF3D-4C3A442C008A@sperl.org> <20151121134946.GI26072@sirena.org.uk> <56507B3B.4080608@gmail.com> <5650F7D4.1090209@gmail.com> <20151122131626.GN26072@sirena.org.uk> <5651EA08.5090400@gmail.com> <20151123113846.GH1929@sirena.org.uk> <5658AE7C.3050507@gmail.com> <20151130164223.GE1929@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Brian Norris , Michal Suchanek , Martin Sperl , MTD Maling List , "linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" To: Mark Brown Return-path: In-Reply-To: <20151130164223.GE1929-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> Sender: linux-spi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Am 30.11.2015 um 17:42 schrieb Mark Brown: > On Fri, Nov 27, 2015 at 08:26:52PM +0100, Heiner Kallweit wrote: >> Am 23.11.2015 um 12:38 schrieb Mark Brown: > >>> No, for the clients so they aren't peering at the struct. > >> Sure, do you think of a simple getter like this or a more complex thing? > >> size_t spi_get_max_msg_size(struct spi_master *master) >> { >> return master->max_msg_size; >> } > > That's fine, the point is to allow it to get complicated later rather > than that we have anything else to put in there right now. > OK, then I'll submit an updated version of the patch. -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html