All of lore.kernel.org
 help / color / mirror / Atom feed
From: subashab@codeaurora.org
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, stranche@codeaurora.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] net: rmnet: several code cleanup for rmnet module
Date: Wed, 04 Mar 2020 16:43:58 -0700	[thread overview]
Message-ID: <eb4fa65d10a8b1f81be44bcb4e3b6a43@codeaurora.org> (raw)
In-Reply-To: <20200304232415.12205-1-ap420073@gmail.com>

On 2020-03-04 16:24, Taehee Yoo wrote:
> This patchset is to cleanup rmnet module code.
> 
> 1. The first patch is to add module alias
> rmnet module can not be loaded automatically because there is no
> alias name.
> 
> 2. The second patch is to add extack error message code.
> When rmnet netlink command fails, it doesn't print any error message.
> So, users couldn't know the exact reason.
> In order to tell the exact reason to the user, the extack error message
> is used in this patch.
> 
> 3. The third patch is to use GFP_KERNEL instead of GFP_ATOMIC.
> In the sleepable context, GFP_KERNEL can be used.
> So, in this patch, GFP_KERNEL is used instead of GFP_ATOMIC.
> 
> Change log:
>  - v1->v2: change error message in the second patch.
> 
> Taehee Yoo (3):
>   net: rmnet: add missing module alias
>   net: rmnet: print error message when command fails
>   net: rmnet: use GFP_KERNEL instead of GFP_ATOMIC
> 
>  .../ethernet/qualcomm/rmnet/rmnet_config.c    | 36 ++++++++++++-------
>  .../net/ethernet/qualcomm/rmnet/rmnet_vnd.c   | 11 +++---
>  .../net/ethernet/qualcomm/rmnet/rmnet_vnd.h   |  3 +-
>  3 files changed, 32 insertions(+), 18 deletions(-)

For the series:

Acked-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>

  reply	other threads:[~2020-03-04 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 23:24 [PATCH net-next v2 0/3] net: rmnet: several code cleanup for rmnet module Taehee Yoo
2020-03-04 23:43 ` subashab [this message]
2020-03-05  2:53   ` Jakub Kicinski
2020-03-05 19:47 ` 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=eb4fa65d10a8b1f81be44bcb4e3b6a43@codeaurora.org \
    --to=subashab@codeaurora.org \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stranche@codeaurora.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 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.