From: Malcolm Priestley <tvboxspy@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] vt6656: [BUG] - Failed connection, incorrect endian. v2
Date: Wed, 29 Aug 2012 23:12:37 +0100 [thread overview]
Message-ID: <1346278357.2177.7.camel@router7789> (raw)
In-Reply-To: <503E8789.6050809@lwfinger.net>
On Wed, 2012-08-29 at 16:20 -0500, Larry Finger wrote:
> On 08/29/2012 03:54 PM, Malcolm Priestley wrote:
> >
> > This patch fixes a bug with driver failing to negotiate a connection.
> >
> > The bug was traced to commit
> > 203e4615ee9d9fa8d3506b9d0ef30095e4d5bc90
> > staging: vt6656: removed custom definitions of Ethernet packet types
> >
> > In that patch, definitions in include/linux/if_ether.h replaced ones
> > in tether.h which had both big and little endian definitions.
> >
> > include/linux/if_ether.h only refers to big endian values, cpu_to_be16
> > should be used for the correct endian architectures.
> >
> > checkpatch fixed version.
> >
> > Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com>
>
> Patches for staging drivers should be sent to gregkh@linuxfoundation.org. He is
> the one that handles them. In addition, the patch subject line usually has the
> sequence "staging: vt6656: blabla" the way the faulty patch did.
Thanks
I have forwarded the patch.
Regards
Malcolm
prev parent reply other threads:[~2012-08-29 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 20:54 [PATCH] vt6656: [BUG] - Failed connection, incorrect endian. v2 Malcolm Priestley
2012-08-29 21:20 ` Larry Finger
2012-08-29 22:12 ` Malcolm Priestley [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=1346278357.2177.7.camel@router7789 \
--to=tvboxspy@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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