public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ramon Fried <rfried.dev@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: make MAX_UIO_MAPS & MAX_UIO_PORT_REGIONS configurable
Date: Wed, 13 Apr 2022 09:27:57 +0200	[thread overview]
Message-ID: <YlZ7fQIpXNJSbd+P@kroah.com> (raw)
In-Reply-To: <20220413071137.4023184-1-rfried.dev@gmail.com>

On Wed, Apr 13, 2022 at 10:11:37AM +0300, Ramon Fried wrote:
> MAX_UIO_MAPS and MAX_UIO_PORT_REGIONS are hard-coded to 5.
> This is not always sufficiant for some drivers.

Why not?  What in-kernel drivers need more than this?

> Make the MAX_UIO_MAPS and MAX_UIO_PORT_REGIONS configurable by
> providing Kconfig int option with the defaut value of 5.

Spelling check?

> 
> Signed-off-by: Ramon Fried <rfried.dev@gmail.com>
> ---
>  drivers/uio/Kconfig        | 14 ++++++++++++++
>  include/linux/uio_driver.h |  4 ++--
>  2 files changed, 16 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/uio/Kconfig b/drivers/uio/Kconfig
> index 2e16c5338e5b..bc1fe83cec13 100644
> --- a/drivers/uio/Kconfig
> +++ b/drivers/uio/Kconfig
> @@ -13,6 +13,20 @@ menuconfig UIO
>  
>  if UIO
>  
> +config UIO_MAX_MAPS
> +	int "Maximum of memory nodes each uio device support(1-128)"

Space before "(" please.

> +	range 1 128
> +	default 5
> +	help
> +	  Maximum memory mapping each uio device can support.

Any hints as to what this means in more detail?

> +
> +config UIO_MAX_PORT_REGIONS
> +	int "Maximum of port regions each uio device support(1-128)"
> +	range 1 128
> +	default 5
> +	help
> +	  Maximum port regions each uio device can support.

Again more detail please.

thanks,

greg k-h

  reply	other threads:[~2022-04-13  7:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  7:11 [PATCH] uio: make MAX_UIO_MAPS & MAX_UIO_PORT_REGIONS configurable Ramon Fried
2022-04-13  7:27 ` Greg KH [this message]
2022-04-13  7:40   ` Ramon Fried
2022-04-13  7:45     ` Greg KH
2022-04-13  7:55       ` Ramon Fried

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=YlZ7fQIpXNJSbd+P@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rfried.dev@gmail.com \
    /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