All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: netdev@vger.kernel.org, Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [PATCH net-next 3/5] mv643xx_eth.c: convert skb->end into skb_end_poitner(skb)
Date: Mon, 17 Jun 2013 11:02:18 +0900	[thread overview]
Message-ID: <20130617020218.GD15043@verge.net.au> (raw)
In-Reply-To: <7629c2a65cffd7b61d100703567e027a2850c3c6.1371200138.git.yamahata@valinux.co.jp>

On Fri, Jun 14, 2013 at 05:58:33PM +0900, Isaku Yamahata wrote:
> The change set of 4305b541 "[SK_BUFF]: Convert skb->end to sk_buff_data_t"
> converted skb->end from pointer to sk_buff_data_t.
> The pointed value should be accessed via skb_end_pointer().
> 
> Since arm or ppc arch doesn't define NET_SKBUFF_DATA_USES_OFFSET,
> skb->end is effectively pointer. So it doesn't cause a real problem.
> But this patch is good for consistency.
> 
> Found by inspection. Compile test only.
> 
> Cc: Simon Horman <horms@verge.net.au>
> Cc: Lennert Buytenhek <buytenh@wantstofly.org>
> Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>

Reviewed-by: Simon Horman <horms@verge.net.au>

> ---
>  drivers/net/ethernet/marvell/mv643xx_eth.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/marvell/mv643xx_eth.c b/drivers/net/ethernet/marvell/mv643xx_eth.c
> index c7f9fb3..510d506 100644
> --- a/drivers/net/ethernet/marvell/mv643xx_eth.c
> +++ b/drivers/net/ethernet/marvell/mv643xx_eth.c
> @@ -621,7 +621,7 @@ static int rxq_refill(struct rx_queue *rxq, int budget)
>  
>  		rx_desc = rxq->rx_desc_area + rx;
>  
> -		size = skb->end - skb->data;
> +		size = skb_end_pointer(skb) - skb->data;
>  		rx_desc->buf_ptr = dma_map_single(mp->dev->dev.parent,
>  						  skb->data, size,
>  						  DMA_FROM_DEVICE);
> -- 
> 1.7.10.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2013-06-17  2:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14  8:58 [PATCH net-next 1/5] net, atm/ambassader: convert skb->tail into skb_tail_pointer(skb) Isaku Yamahata
2013-06-14  8:58 ` [PATCH net-next 2/5] net, scsi/csgb4i: convert skb->transport_header into skb_transport_header(skb) Isaku Yamahata
2013-06-17  2:04   ` Simon Horman
2013-06-18  0:13     ` David Miller
2013-06-14  8:58 ` [PATCH net-next 3/5] mv643xx_eth.c: convert skb->end into skb_end_poitner(skb) Isaku Yamahata
2013-06-17  2:02   ` Simon Horman [this message]
2013-06-18  0:13     ` David Miller
2013-06-14  8:58 ` [PATCH net-next 4/5] pxa168_eth: convert skb->end into skb_end_pointer(skb) Isaku Yamahata
2013-06-17  2:01   ` Simon Horman
2013-06-18  0:13     ` David Miller
2013-06-14  8:58 ` [PATCH net-next 5/5] staging/rtl8192u: convert skb->tail into skb_tail_pointer(skb) Isaku Yamahata
2013-06-17  2:03   ` Simon Horman
2013-06-18  0:13     ` David Miller
2013-06-17 22:45   ` Greg Kroah-Hartman
2013-06-17  2:01 ` [PATCH net-next 1/5] net, atm/ambassader: " Simon Horman
2013-06-18  0:13   ` 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=20130617020218.GD15043@verge.net.au \
    --to=horms@verge.net.au \
    --cc=buytenh@wantstofly.org \
    --cc=netdev@vger.kernel.org \
    --cc=yamahata@valinux.co.jp \
    /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.