From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/4] net: qualcomm: rmnet: Updates 2018-03-12
Date: Wed, 14 Mar 2018 13:27:41 -0600 [thread overview]
Message-ID: <a099fdae0a1b6def9ac7db6bcafaf664@codeaurora.org> (raw)
In-Reply-To: <20180314.140615.802964606635535521.davem@davemloft.net>
> Please address Joe's feedback and only update the copyright date on
> files that actually had changes this year.
>
> Thank you.
Hi David
I have fixed that now in v3.
However, patchwork is not showing the entire series.
It shows only the first patch for some reason even if I search with me
as submitter.
https://patchwork.ozlabs.org/project/netdev/list/?submitter=65547&state=%2A&archive=both
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-03-14 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 22:50 [PATCH net-next v2 0/4] net: qualcomm: rmnet: Updates 2018-03-12 Subash Abhinov Kasiviswanathan
2018-03-13 22:50 ` [PATCH net-next v2 1/4] net: qualcomm: rmnet: Fix casting issues Subash Abhinov Kasiviswanathan
2018-03-13 22:50 ` [PATCH net-next v2 2/4] net: qualcomm: rmnet: Update copyright year to 2018 Subash Abhinov Kasiviswanathan
2018-03-13 23:32 ` Joe Perches
2018-03-14 0:15 ` Subash Abhinov Kasiviswanathan
2018-03-14 0:20 ` Joe Perches
2018-03-13 22:50 ` [PATCH net-next v2 3/4] net: qualcomm: rmnet: Remove unnecessary device assignment Subash Abhinov Kasiviswanathan
2018-03-13 22:50 ` [PATCH net-next v2 4/4] net: qualcomm: rmnet: Implement fill_info Subash Abhinov Kasiviswanathan
2018-03-14 18:06 ` [PATCH net-next v2 0/4] net: qualcomm: rmnet: Updates 2018-03-12 David Miller
2018-03-14 19:27 ` Subash Abhinov Kasiviswanathan [this message]
2018-03-15 1:29 ` David Miller
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=a099fdae0a1b6def9ac7db6bcafaf664@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).