All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Brogi <gui-gui@netcourrier.com>
To: Greg Kroah-Hartman <greg@kroah.com>
Cc: Bhumika Goyal <bhumirks@gmail.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192u: Convert __le16 to cpu before casting to u32
Date: Fri, 12 May 2017 22:09:35 +0200	[thread overview]
Message-ID: <20170512200935.o2npfrrgslhd2b7d@nexon> (raw)
In-Reply-To: <20170512080835.GB15405@kroah.com>

> > Since there was no news for a while, I figured I'd ask what's the status
> > of this patch. I hope that's OK. Has it simply been forgotten or is
> > there something blocking/unacceptable?
> 
> I don't see it in my queue, sorry.  If you can't test this, or verify
> that it is correct some other way, I don't want to take endian fixes,
> sorry.
> 
No worries. I figured that was a possibility after your comments.
I figured running sparse and trying to fix errors in staging could be a
good starting point, but apparently it is not (I don't think I have any
of the exotic hardware in staging). Is there anywhere else I could get
started? Or are there other errors from sparse which are less likely to
be complex to check and hence require hardware to test the changes?

Cheers,

-- 
Guillaume

      reply	other threads:[~2017-05-12 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-25 23:24 [PATCH] Convert __le16 to cpu before casting to u32 Guillaume Brogi
2017-04-08 10:31 ` Greg Kroah-Hartman
2017-04-08 18:32   ` [PATCH] staging: rtl8192u: " Guillaume Brogi
2017-05-07 12:56     ` Guillaume Brogi
2017-05-12  8:08       ` Greg Kroah-Hartman
2017-05-12 20:09         ` Guillaume Brogi [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=20170512200935.o2npfrrgslhd2b7d@nexon \
    --to=gui-gui@netcourrier.com \
    --cc=bhumirks@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --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 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.