[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76a0c445-c345-fdf4-12b1-974491f6a77e@suse.com>
Date: Tue, 1 Nov 2016 05:33:01 +0100
From: Juergen Gross <jgross@...e.com>
To: David Miller <davem@...emloft.net>
Cc: linux-kernel@...r.kernel.org, xen-devel@...ts.xen.org,
david.vrabel@...rix.com, boris.ostrovsky@...cle.com,
konrad.wilk@...cle.com, roger.pau@...rix.com, peterhuewe@....de,
tpmdd@...horst.net, jarkko.sakkinen@...ux.intel.com,
jgunthorpe@...idianresearch.com, tpmdd-devel@...ts.sourceforge.net,
dmitry.torokhov@...il.com, linux-input@...r.kernel.org,
wei.liu2@...rix.com, paul.durrant@...rix.com,
netdev@...r.kernel.org, bhelgaas@...gle.com,
linux-pci@...r.kernel.org, tomi.valkeinen@...com,
linux-fbdev@...r.kernel.org
Subject: Re: [PATCH 00/12] xen: add common function for reading optional value
On 31/10/16 18:08, David Miller wrote:
> From: Juergen Gross <jgross@...e.com>
> Date: Mon, 31 Oct 2016 17:48:18 +0100
>
>> There are multiple instances of code reading an optional unsigned
>> parameter from Xenstore via xenbus_scanf(). Instead of repeating the
>> same code over and over add a service function doing the job and
>> replace the call of xenbus_scanf() with the call of the new function
>> where appropriate.
>
> As this seems to be a series that will go through some tree other
> than mine, I assume the networking bits will be taken care of that
> way.
>
If accepted I expect this series to go through the Xen tree.
Juergen
Powered by blists - more mailing lists