linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peng Sun <sironhide0null@gmail.com>
To: liodot@gmail.com, charrer@alacritech.com, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, Peng Sun <sironhide0null@gmail.com>
Subject: [PATCH 00/10] staging: slicoss: fix different address space sparse warnings
Date: Tue, 13 Sep 2016 19:59:49 -0700	[thread overview]
Message-ID: <cover.1473821899.git.sironhide0null@gmail.com> (raw)

base commit-id d221eb9f14f9

Peng Sun (10):
  staging: slicoss: slic.h: add a macro IOMEM_GET_FIELDADDR to fix
    sparse warnings
  staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD32 to fix sparse
    warnings
  staging: slicoss: slic.h: add a macro IOMEM_SET_FIELD32 to fix sparse
    warnings
  staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD64 to fix sparse
    warnings
  staging: slicoss: slicoss.c: fix different address space sparse
    warning
  staging: slicoss: slicoss.c: fix different address space sparse
    warning
  staging: slicoss: slicoss.c: fix different address space sparse
    warning
  staging: slicoss: slicoss.c: fix different address space sparse
    warning
  staging: slicoss: slicoss.c: fix different address space sparse
    warning
  staging: slicoss: slicoss.c: fix different address space sparse
    warning

 drivers/staging/slicoss/slic.h    | 46 ++++++++++++++++++++++
 drivers/staging/slicoss/slicoss.c | 82 +++++++++++++++++++++++----------------
 2 files changed, 95 insertions(+), 33 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-09-14  3:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14  2:59 Peng Sun [this message]
2016-09-14  2:59 ` [PATCH 01/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELDADDR to fix sparse warnings Peng Sun
2016-09-14  2:59   ` [PATCH 02/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD32 " Peng Sun
2016-09-14  2:59     ` [PATCH 03/10] staging: slicoss: slic.h: add a macro IOMEM_SET_FIELD32 " Peng Sun
2016-09-14  2:59       ` [PATCH 04/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD64 " Peng Sun
2016-09-14  2:59         ` [PATCH 05/10] staging: slicoss: slicoss.c: fix different address space sparse warning Peng Sun
2016-09-14  2:59           ` [PATCH 06/10] " Peng Sun
2016-09-14  2:59             ` [PATCH 07/10] " Peng Sun
2016-09-14  2:59               ` [PATCH 08/10] " Peng Sun
2016-09-14  2:59                 ` [PATCH 09/10] " Peng Sun
2016-09-14  2:59                   ` [PATCH 10/10] " Peng Sun
2016-09-16  7:52   ` [PATCH 01/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELDADDR to fix sparse warnings Greg KH
2016-09-16  7:52   ` Greg KH
2016-09-16 10:41     ` zerons
2016-09-16 12:57       ` Greg KH
2016-09-16 13:54         ` zerons

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=cover.1473821899.git.sironhide0null@gmail.com \
    --to=sironhide0null@gmail.com \
    --cc=charrer@alacritech.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liodot@gmail.com \
    /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).