linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bhaskar Singh <bhaskar.kernel@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8188eu: Removed a function and coded inline
Date: Mon, 20 Aug 2018 21:33:04 +0530	[thread overview]
Message-ID: <20180820160304.GA7500@Gentoo-PC> (raw)
In-Reply-To: <20180820093546.whlekjpoqluqfeq2@mwanda>

On Mon, Aug 20, 2018 at 12:35:46PM +0300, Dan Carpenter wrote:
> On Sun, Aug 19, 2018 at 12:36:40AM +0530, Bhaskar Singh wrote:
> > This patch removed function named rtw_malloc2d.
> > 
> > I removed this function because this function is used exactly once and
> > function call have some overhead also.
> > 
> > Maybe this will improve code runtime slightly.
> > 
> > Signed-off-by: Bhaskar Singh <bhaskar.kernel@gmail.com>
> > ---
> >  drivers/staging/rtl8188eu/core/rtw_efuse.c        | 10 +++++++++-
> >  drivers/staging/rtl8188eu/include/osdep_service.h |  2 --
> >  drivers/staging/rtl8188eu/os_dep/osdep_service.c  | 14 --------------
> >  3 files changed, 9 insertions(+), 17 deletions(-)
> > 
> > diff --git a/drivers/staging/rtl8188eu/core/rtw_efuse.c b/drivers/staging/rtl8188eu/core/rtw_efuse.c
> > index 0fd306a808c4..befc99c197b1 100644
> > --- a/drivers/staging/rtl8188eu/core/rtw_efuse.c
> > +++ b/drivers/staging/rtl8188eu/core/rtw_efuse.c
> > @@ -86,12 +86,20 @@ efuse_phymap_to_logical(u8 *phymap, u16 _offset, u16 _size_byte, u8  *pbuf)
> >  	u16	**eFuseWord = NULL;
> >  	u16	efuse_utilized = 0;
> >  	u8 u1temp = 0;
> > +	int z;
> 
> z is unusual name for an iterator.  Does it stand for something?  Just
> use "int i;".
> 
> > +	void **a = NULL;
> 
> What does "a" mean in this context?  Maybe just say "void **tmp;"
> 
> >  
> >  	efuseTbl = kzalloc(EFUSE_MAP_LEN_88E, GFP_KERNEL);
> >  	if (!efuseTbl)
> >  		return;
> >  
> > -	eFuseWord = (u16 **)rtw_malloc2d(EFUSE_MAX_SECTION_88E, EFUSE_MAX_WORD_UNIT, sizeof(u16));
> > +	a = kzalloc(EFUSE_MAX_SECTION_88E * sizeof(void *) + EFUSE_MAX_SECTION_88E * EFUSE_MAX_WORD_UNIT * sizeof(u16), GFP_KERNEL);
> > +	if (!a)
> > +		goto out;
> 
> 
> You can simplify the math a bit:
> 
> 	tmp = kzalloc(EFUSE_MAX_SECTION_88E * (sizeof(void *) + EFUSE_MAX_WORD_UNIT * sizeof(u16)), GFP_KERNEL);
> 
> Then if it fails:
> 
> 	if (!tmp)
> 		goto eFuseWord_failed;
> 
> 
> regards,
> dan carpenter
>

Here I have modified 3 files but after seeing comments of Dan Carpenter
I have edited one file. What to do with those 2 files which I haven't
modified while sending 2nd version of this patch because all three file
combinedly making one logical change.
I apologies, if this is not the right place for asking this type of questions

      reply	other threads:[~2018-08-20 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-18 19:06 [PATCH] staging: rtl8188eu: Removed a function and coded inline Bhaskar Singh
2018-08-20  9:35 ` Dan Carpenter
2018-08-20 16:03   ` Bhaskar Singh [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=20180820160304.GA7500@Gentoo-PC \
    --to=bhaskar.kernel@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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).