All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Aiuto <fabioaiuto83@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Wenlong Zhang <yixiaonn@gmail.com>,
	gregkh@linuxfoundation.org, ross.schm.dev@gmail.com,
	marcocesati@gmail.com, insafonov@gmail.com, cyruscyliu@gmail.com,
	yajin@vm-kernel.org, linux-kernel@vger.kernel.org,
	linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: prevent ->ssid overflow in rtw_wx_set_scan()
Date: Fri, 27 Aug 2021 08:46:44 +0200	[thread overview]
Message-ID: <20210827064644.GA1408@agape.jhs> (raw)
In-Reply-To: <20210826181648.GC1931@kadam>

On Thu, Aug 26, 2021 at 09:16:48PM +0300, Dan Carpenter wrote:
> On Thu, Aug 26, 2021 at 07:26:19PM +0200, Fabio Aiuto wrote:
> > today the patch which removes wext handlers has been accepted
> > (commit 174ac41a7aafb31041cba3fe54ccd89b9daeef5d)
> > in staging-testing so maybe rtw_wx_set_scan is going to disappear.
> > 
> 
> From a process perspective, in staging we don't track things that might
> happen in the future.  We look at each patch in the order that they
> arrive and either apply them or reject them.

Wenlong's patch will be applied on top of staging-testing first,
and it won't apply due to wext-removal patch.

> 
> And from a practical perspective this patch might be something that
> people want to backport so it would be nice to apply it.
> 
> regards,
> dan carpenter

thank you,

fabio

  reply	other threads:[~2021-08-27  6:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 15:46 [PATCH] staging: rtl8723bs: prevent ->ssid overflow in rtw_wx_set_scan() Wenlong Zhang
2021-08-26 16:59 ` Dan Carpenter
2021-08-26 17:19 ` Fabio Aiuto
2021-08-26 17:26 ` Fabio Aiuto
2021-08-26 18:16   ` Dan Carpenter
2021-08-27  6:46     ` Fabio Aiuto [this message]
2021-08-26 18:55 ` Greg KH
2021-08-27  9:00   ` [PATCH v2] " Wenlong Zhang
2021-08-27  9:47     ` Greg KH
2021-08-27 12:50   ` [PATCH v3] " Wenlong Zhang
2021-08-27 13:06     ` Dan Carpenter
2021-08-27 13:10     ` Greg KH

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=20210827064644.GA1408@agape.jhs \
    --to=fabioaiuto83@gmail.com \
    --cc=cyruscyliu@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=insafonov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=marcocesati@gmail.com \
    --cc=ross.schm.dev@gmail.com \
    --cc=yajin@vm-kernel.org \
    --cc=yixiaonn@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 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.