From: Dan Carpenter <dan.carpenter@linaro.org>
To: Calvince Otieno <calvncce@gmail.com>
Cc: outreachy@lists.linux.dev, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.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: Mon, 16 Oct 2023 11:46:40 +0300 [thread overview]
Message-ID: <d50d6a13-c27c-4e9f-8728-e3ad3e4d94db@kadam.mountain> (raw)
In-Reply-To: <4c29cb7a-3b24-4682-9211-09aff1e01360@kadam.mountain>
On Mon, Oct 16, 2023 at 07:40:57AM +0300, Dan Carpenter wrote:
> 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?
>
> Ugh... No, sorry. I suck at emails. White space damaged is not good.
> I left out the word not... :/
>
> You need to figure out what's going on there. Some of your patches are
> not white space damaged so sometimes you're doing it right but here the
> spaces were replaced with tabs so it doesn't apply.
Wow... I absolutely suck at writing emails and *reading emails*. This
wasn't the white space damaged patch. This was the okay one.
However you sent a v2 patch in the wrong way. You just posted a fixup
instead of resending the patch. You've sent v2 patches before but let
me send you my blog link anyway...
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/
regards,
dan carpenter
prev parent reply other threads:[~2023-10-16 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 10:50 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
2023-10-16 4:40 ` Dan Carpenter
2023-10-16 8:46 ` Dan Carpenter [this message]
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=d50d6a13-c27c-4e9f-8728-e3ad3e4d94db@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=bagasdotme@gmail.com \
--cc=calvncce@gmail.com \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®