From: Ganapathi Bhat <gbhat@marvell.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Rakesh Parmar <rakeshp@marvell.com>, James Cao <jcao@marvell.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Not able to see patches in patchwork
Date: Wed, 9 Jan 2019 15:01:39 +0000 [thread overview]
Message-ID: <CY4PR18MB1237311E8A5B1D719BB48EB5A08B0@CY4PR18MB1237.namprd18.prod.outlook.com> (raw)
In-Reply-To: <87ef9nqdea.fsf@kamboji.qca.qualcomm.com>
Hi Kalle,
> Hi Ganapathi,
>
> please do not email me privately. If you have questions send them to the list,
> you get answers faster and I get less email :)
Ok, sure.
>
> Ganapathi Bhat <gbhat@marvell.com> writes:
>
> > I am not able to see the patch sent to
> > 'linux-wireless.vger.kernel.org', in
> > https://patchwork.kernel.org/project/linux-wireless/list/
> >
> > Let me know if you received my patch, named "mwifiex: add support for
> > sd8977 chipset"
>
> When did you submit it?
I did submit it couple of weeks before, using 'git send-mail' utility.
> I don't see such email on linux-wireless list.
> I recommend resubmitting the patch as v2.
Ok. I have sent v2 using my GUI mail client. Now we could see in the linux-wireless list.
Sorry for the trouble(could have tried this first).
Thanks,
Ganapathi
next prev parent reply other threads:[~2019-01-09 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CY4PR18MB12372AF071013F01A0DE6A32A08A0@CY4PR18MB1237.namprd18.prod.outlook.com>
2019-01-08 17:15 ` Not able to see patches in patchwork Kalle Valo
2019-01-09 15:01 ` Ganapathi Bhat [this message]
2019-01-09 15:35 ` Kalle Valo
2019-01-10 8:38 ` Ganapathi Bhat
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=CY4PR18MB1237311E8A5B1D719BB48EB5A08B0@CY4PR18MB1237.namprd18.prod.outlook.com \
--to=gbhat@marvell.com \
--cc=jcao@marvell.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rakeshp@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).