All of lore.kernel.org
 help / color / mirror / Atom feed
From: Deepak R Varma <drv@mailo.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: staging/wlan-ng query: convert to flexible array member
Date: Wed, 9 Nov 2022 12:21:30 +0530	[thread overview]
Message-ID: <Y2tN8u5zwH5Ufkgd@qemulion> (raw)
In-Reply-To: <Y2qxeDQ+76CvfN1c@kroah.com>

On Tue, Nov 08, 2022 at 08:43:52PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Nov 09, 2022 at 12:08:41AM +0530, Deepak R Varma wrote:
> > On Tue, Nov 08, 2022 at 07:32:19PM +0100, Greg Kroah-Hartman wrote:
> > > > > Test the device to make sure it still works?
> > > >
> > > > I was able to build and load the driver on my machine. I do not have p54 device
> > > > to test. Is there another way to test it? Some sort of a udev program???
> > >
> > > You need the real hardware to test it properly.
> >
> > Do you know if I work with someone to test the change locally rather than
> > sending in a untested change?
>
> If you can find someone, sure!

Hello Greg,
I reached out to couple of recent patch authors to check if they are able to
help test the change.

Hello all,
Does anyone have a hardware that can test prism2_usb [wlan-ng] driver change? I
assume it would be quick to test the change I am proposing. Let me know if you
are able to help.

Thank you!
./drv


>



  reply	other threads:[~2022-11-09  6:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 15:12 staging/wlan-ng query: convert to flexible array member Deepak R Varma
2022-11-08 15:34 ` Greg Kroah-Hartman
2022-11-08 15:45   ` Deepak R Varma
2022-11-08 15:52     ` Greg Kroah-Hartman
2022-11-08 17:37       ` Deepak R Varma
2022-11-08 18:32         ` Greg Kroah-Hartman
2022-11-08 18:38           ` Deepak R Varma
2022-11-08 19:43             ` Greg Kroah-Hartman
2022-11-09  6:51               ` Deepak R Varma [this message]
2022-11-13  6:33 ` Gustavo A. R. Silva
2022-11-13  7:38   ` Deepak R Varma

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=Y2tN8u5zwH5Ufkgd@qemulion \
    --to=drv@mailo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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.