From: Greg KH <gregkh@linuxfoundation.org>
To: Bogicevic Sasa <brutallesale@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers:staging:gdm72xx Fix increment in a loop
Date: Sat, 31 Oct 2015 16:59:06 -0700 [thread overview]
Message-ID: <20151031235906.GD10644@kroah.com> (raw)
In-Reply-To: <1446328980-1016-1-git-send-email-brutallesale@gmail.com>
On Sat, Oct 31, 2015 at 11:03:00PM +0100, Bogicevic Sasa wrote:
> This fixes increment of pos int to be more readable
> Lines qcb->csr[index].srcport_lo = ((buf[pos++]<<8)&0xff00);
> qcb->csr[index].srcport_lo += buf[pos++];
> become
> qcb->csr[index].srcport_lo = get_unaligned_le16(&buf[pos]);
> pos += 2;
>
> Signed-off-by: Bogicevic Sasa <brutallesale@gmail.com>
> ---
> drivers/staging/gdm72xx/gdm_qos.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
I'm totally confused, please resend all of these patches, numbered in
order, so I have a chance to know how to apply them. Also please always
cc: the proper mailing lists for staging patches (hint, not lkml).
thanks,
greg k-h
prev parent reply other threads:[~2015-10-31 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 22:03 [PATCH] drivers:staging:gdm72xx Fix increment in a loop Bogicevic Sasa
2015-10-31 23:59 ` Greg KH [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=20151031235906.GD10644@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=brutallesale@gmail.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 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).