From: Dan Carpenter <dan.carpenter@oracle.com>
To: Ivan Safonov <insafonov@gmail.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Nishka Dasgupta <nishkadg.linux@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Soumyajit Deb <debsoumyajit100@gmail.com>
Subject: Re: [PATCH] staging: r8188eu: remove unused members of struct xmit_buf
Date: Mon, 13 Jul 2020 17:23:05 +0300 [thread overview]
Message-ID: <20200713142305.GV2549@kadam> (raw)
In-Reply-To: <20200713131607.GR2549@kadam>
On Mon, Jul 13, 2020 at 04:16:07PM +0300, Dan Carpenter wrote:
> On Sun, Jul 12, 2020 at 03:38:21PM +0300, Ivan Safonov wrote:
> > Remove unused members of struct xmit_buf: alloc_sz, ff_hwaddr,
> > dma_transfer_addr, bpending and last.
> >
> > Signed-off-by: Ivan Safonov <insafonov@gmail.com>
> > ---
> > drivers/staging/rtl8188eu/include/rtw_xmit.h | 5 -----
> > drivers/staging/rtl8188eu/os_dep/xmit_linux.c | 1 -
> > 2 files changed, 6 deletions(-)
> >
> > diff --git a/drivers/staging/rtl8188eu/include/rtw_xmit.h b/drivers/staging/rtl8188eu/include/rtw_xmit.h
> > index 12d16e98176a..3c03987c81a1 100644
> > --- a/drivers/staging/rtl8188eu/include/rtw_xmit.h
> > +++ b/drivers/staging/rtl8188eu/include/rtw_xmit.h
> > @@ -193,14 +193,9 @@ struct xmit_buf {
> > void *priv_data;
> > u16 ext_tag; /* 0: Normal xmitbuf, 1: extension xmitbuf. */
> > u16 flags;
> > - u32 alloc_sz;
> > u32 len;
> > struct submit_ctx *sctx;
> > - u32 ff_hwaddr;
> > struct urb *pxmit_urb[8];
> > - dma_addr_t dma_transfer_addr; /* (in) dma addr for transfer_buffer */
> > - u8 bpending[8];
> > - int last[8];
> > };
> >
> > struct xmit_frame {
> > diff --git a/drivers/staging/rtl8188eu/os_dep/xmit_linux.c b/drivers/staging/rtl8188eu/os_dep/xmit_linux.c
> > index 017e1d628461..61ced1160951 100644
> > --- a/drivers/staging/rtl8188eu/os_dep/xmit_linux.c
> > +++ b/drivers/staging/rtl8188eu/os_dep/xmit_linux.c
> > @@ -24,7 +24,6 @@ int rtw_os_xmit_resource_alloc(struct adapter *padapter,
> > return _FAIL;
> >
> > pxmitbuf->pbuf = PTR_ALIGN(pxmitbuf->pallocated_buf, XMITBUF_ALIGN_SZ);
>
> Not related to this patch but kmalloc always returns data which is at
> least ARCH_KMALLOC_MINALIGN aligned which is never less than
> XMITBUF_ALIGN_SZ (4) so this is a no-op.
The alignment in the driver is pretty crazy because it's all unnecessary
and so complicated. Every allocation is 4 bytes extra so we can align
it later.
Also every buffer is called "pbuf" which stands for pointer to buffer.
"pallocated_buf" is not really useful either.
I tried to look at this to see if we could change the alignment, and
it's complicated because of the naming and the alignment.
regards,
dan carpenter
next prev parent reply other threads:[~2020-07-13 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 12:38 [PATCH] staging: r8188eu: remove unused members of struct xmit_buf Ivan Safonov
2020-07-12 17:55 ` Larry Finger
2020-07-12 21:11 ` Ivan Safonov
2020-07-13 13:16 ` Dan Carpenter
2020-07-13 14:23 ` Dan Carpenter [this message]
2020-07-13 18:28 ` Ivan Safonov
2020-07-13 21:15 ` Larry Finger
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=20200713142305.GV2549@kadam \
--to=dan.carpenter@oracle.com \
--cc=Larry.Finger@lwfinger.net \
--cc=debsoumyajit100@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=insafonov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nishkadg.linux@gmail.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