All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ernestas Kulik <ernestas.kulik@gmail.com>
To: Joe Perches <joe@perches.com>, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: ks7010: clean up code
Date: Sat, 4 Mar 2017 11:04:30 +0200	[thread overview]
Message-ID: <20170304090429.GA2093@gmail.com> (raw)
In-Reply-To: <1488612271.2179.48.camel@perches.com>

On Fri, 2017-03-03 at 23:24-0800, Joe Perches wrote:
>
> More stuff the changelog doesn't show :(
>
> On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote:
> > This fixes type warnings generated by sparse, replaces instances of
> > ntohs() with be16_to_cpu() and removes unused fields in structs.

I’ve posted a v2 of the patch, reducing the scope so as to not
inadvertently break something.

      reply	other threads:[~2017-03-04  9:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 20:58 [PATCH] staging: ks7010: clean up code Ernestas Kulik
2017-03-04  1:23 ` Joe Perches
2017-03-04  6:28   ` Ernestas Kulik
2017-03-04  6:37     ` Joe Perches
2017-03-04  6:49       ` Ernestas Kulik
2017-03-04  7:24         ` Joe Perches
2017-03-04  9:04           ` Ernestas Kulik [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=20170304090429.GA2093@gmail.com \
    --to=ernestas.kulik@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.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.