All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Osama Muhammad <osmtendev@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [PATCH] Accessiblity: speakup_bns: specifying the default driver parameters among the module params
Date: Wed, 9 Nov 2022 15:18:14 +0100	[thread overview]
Message-ID: <Y2u2plss5ykqwa4S@kroah.com> (raw)
In-Reply-To: <20221022185600.3989-1-osmtendev@gmail.com>

On Sat, Oct 22, 2022 at 11:56:00PM +0500, Osama Muhammad wrote:
> This is an enhancement which allows to specify the default driver
> parameters among the module parameters.
> 
> Adding a default variables to the speakup_bns module
> allows to easily set that at boot, rather than
> setting the sys variables after boot.
> More details can be found here:
> https://github.com/linux-speakup/speakup/issues/7
> 
> Signed-off-by: Osama Muhammad <osmtendev@gmail.com>
> 
> Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>

Please do not put a blank line between these here.

And is this a v2 patch?

I have a bunch of patches from you, but I can't tell which ones is the
latest ones, and which to drop.

Can you send these all as a patch series so that I know the order in
which to apply them, and to be sure that I have the latest versions?
I'll drop all of your pending patches from my review queue now.

thanks,

greg k-h

  reply	other threads:[~2022-11-09 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 18:56 [PATCH] Accessiblity: speakup_bns: specifying the default driver parameters among the module params Osama Muhammad
2022-11-09 14:18 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-21 13:53 Osama Muhammad
2022-10-22 14:31 ` Samuel Thibault

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=Y2u2plss5ykqwa4S@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osmtendev@gmail.com \
    --cc=samuel.thibault@ens-lyon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.