From: Johannes Postma <jgmpostma@gmail.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
devel@driverdev.osuosl.org,
Larry Finger <Larry.Finger@lwfinger.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] staging: rtl8723au: Fix sparse warning: cast to restricted __le16
Date: Fri, 7 Aug 2015 14:08:55 +0100 [thread overview]
Message-ID: <20150807130855.GA9880@goofy_linux.Home> (raw)
In-Reply-To: <wrfj1tff2sjq.fsf@redhat.com>
On 07/08/15 at 08:26am, Jes Sorensen wrote:
> Johannes Postma <jgmpostma@gmail.com> writes:
> > On 06/08/15 at 08:21am, Jes Sorensen wrote:
> >>
> >> Looks OK to me. Probably worth changing the *(usPtr + index) to be
> >> usPtr[index] as well to make the code easier to read.
> >>
> >> Jes
> >>
> >
> > Thank you for reviewing. I will make a seperate patch for that. I will
> > send it after this one is accepted. Or should I combine them into a
> > patch serie?
>
> Either is fine with me.
>
> Jes
Ok, I have sent it as a separate patch. Since it doesn't depend on this
patch and should apply cleanly I have already sent it in.
Johannes
next prev parent reply other threads:[~2015-08-07 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:21 [PATCH] staging: rtl8723au: Fix sparse warning: cast to restricted __le16 Johannes Postma
2015-08-06 12:21 ` Jes Sorensen
2015-08-07 8:37 ` Johannes Postma
2015-08-07 12:26 ` Jes Sorensen
2015-08-07 13:08 ` Johannes Postma [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-11 17:21 [PATCH] staging: rtl8723au: Fix sparse warning " Marcus Folkesson
2015-03-11 18:23 ` Jes Sorensen
2014-11-18 1:45 [PATCH] staging:rtl8723au: " Tobenna P. Igwe
2014-11-18 1:59 ` Greg KH
2014-11-18 2:51 ` Tobenna Peter, Igwe
2014-11-18 4:06 ` Greg KH
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=20150807130855.GA9880@goofy_linux.Home \
--to=jgmpostma@gmail.com \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.