From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Jeroen Roovers <jer@airfi.aero>
Cc: linux-wireless@vger.kernel.org,
Helmut Schaa <helmut.schaa@googlemail.com>
Subject: Re: [PATCH 3/3] rt2x00: remove queue_entry from skbdesc
Date: Thu, 9 Feb 2017 16:02:22 +0100 [thread overview]
Message-ID: <20170209150221.GA10105@redhat.com> (raw)
In-Reply-To: <CANCHnQq0111TX8psb4YizjSzOOUQSxj6Cf7OX8+L60J83wudsQ@mail.gmail.com>
On Thu, Feb 09, 2017 at 04:00:19PM +0100, Jeroen Roovers wrote:
> On 8 February 2017 at 13:51, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
>
> > diff --git a/drivers/net/wireless/ralink/rt2x00/rt2x00queue.h b/drivers/net/wireless/ralink/rt2x00/rt2x00queue.h
> > index 2233b91..22d1881 100644
> > --- a/drivers/net/wireless/ralink/rt2x00/rt2x00queue.h
> > +++ b/drivers/net/wireless/ralink/rt2x00/rt2x00queue.h
> > @@ -116,8 +116,6 @@ struct skb_frame_desc {
> > __le32 iv[2];
> >
> > dma_addr_t skb_dma;
> > -
> > - struct queue_entry *entry;
> > };
> >
> > /**
>
> That change needs this line removed above:
>
> * @entry: The entry to which this sk buffer belongs.
Thanks, I will fix comments when post next rt2x00 patch series.
Stanislaw
prev parent reply other threads:[~2017-02-09 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 12:51 [PATCH 0/3] rt2x00 skb_desc cleanup Stanislaw Gruszka
2017-02-08 12:51 ` [PATCH 1/3] rt61pci: use entry directly Stanislaw Gruszka
2017-02-08 15:31 ` [1/3] " Kalle Valo
2017-02-08 12:51 ` [PATCH 2/3] rt2x00: call entry directly in rt2x00_dump_frame Stanislaw Gruszka
2017-02-09 14:34 ` Jeroen Roovers
2017-02-08 12:51 ` [PATCH 3/3] rt2x00: remove queue_entry from skbdesc Stanislaw Gruszka
2017-02-09 15:00 ` Jeroen Roovers
2017-02-09 15:02 ` Stanislaw Gruszka [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=20170209150221.GA10105@redhat.com \
--to=sgruszka@redhat.com \
--cc=helmut.schaa@googlemail.com \
--cc=jer@airfi.aero \
--cc=linux-wireless@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).