From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Calvince Otieno <calvncce@gmail.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
outreachy@lists.linux.dev, linux-kernel@vger.kernel.org,
Luke Koch <lu.ale.koch@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Simon Horman <horms@kernel.org>,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v2] staging: wlan-ng: remove helper function prism2sta_inf_handover()
Date: Sun, 15 Oct 2023 18:11:44 +0200 [thread overview]
Message-ID: <2023101537-repair-natural-3218@gregkh> (raw)
In-Reply-To: <CADFX3ORVXcEBzovdbPawW2SLxcMoraKBmmLuOFkMpnHj=T48qQ@mail.gmail.com>
On Fri, Oct 13, 2023 at 07:04:56PM +0300, Calvince Otieno wrote:
> On Fri, Oct 13, 2023 at 3:12 PM Dan Carpenter <dan.carpenter@linaro.org> wrote:
> >
> > On Fri, Oct 13, 2023 at 01:50:23PM +0300, Calvince Otieno wrote:
> > > prism2sta_inf_handover() function basically calls pr_debug() to print
> > > a literal string. This can be done by the parent function directly.
> > >
> > > Signed-off-by: Calvince Otieno <calvncce@gmail.com>
> > > ---
> > > Patch version v2:
> > > - Replace pr_debug() utility function with the module specific netdev_dbg()
> >
> > This isn't a v2 patch, right? This patch assumes that we applied the
> > v1 patch...
> >
> > This patch is not white space damaged though so that's good.
> >
> > regards,
> > dan carpenter
> >
> >
>
> Hello Dan,
> Does this response mean that the patch was accepted?
No, sorry.
next prev parent reply other threads:[~2023-10-15 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:50 [PATCH v2] staging: wlan-ng: remove helper function prism2sta_inf_handover() Calvince Otieno
2023-10-13 11:21 ` Andi Shyti
2023-10-13 12:12 ` Dan Carpenter
2023-10-13 16:04 ` Calvince Otieno
2023-10-15 16:11 ` Greg Kroah-Hartman [this message]
2023-10-16 4:40 ` Dan Carpenter
2023-10-16 8:46 ` Dan Carpenter
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=2023101537-repair-natural-3218@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=calvncce@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lu.ale.koch@gmail.com \
--cc=outreachy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox