All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Peng Sun <sironhide0null@gmail.com>
Cc: liodot@gmail.com, charrer@alacritech.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] staging: slicoss: fix different address space sparse warnings
Date: Sat, 17 Sep 2016 10:30:15 +0200	[thread overview]
Message-ID: <20160917083015.GA16671@kroah.com> (raw)
In-Reply-To: <1474077952-9265-1-git-send-email-sironhide0null@gmail.com>

On Fri, Sep 16, 2016 at 07:05:45PM -0700, Peng Sun wrote:
> commit-id d221eb9f14f9, "Add linux-next specific files for 20160909"
> 
> add several macros to fix these warnings
> 
> Peng Sun (7):
>   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
>   staging: slicoss: slicoss.c: fix different address space sparse
>     warning

All of these had the identical subject: line, but they do different
things!  Please fix them up and make them unique.

thanks,

greg k-h

      parent reply	other threads:[~2016-09-17  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17  2:05 [PATCH 0/7] staging: slicoss: fix different address space sparse warnings Peng Sun
2016-09-17  2:05 ` [PATCH 1/7] staging: slicoss: slicoss.c: fix different address space sparse warning Peng Sun
2016-09-17  2:05 ` [PATCH 2/7] " Peng Sun
2016-09-17  2:05 ` [PATCH 3/7] " Peng Sun
2016-09-17  2:05 ` [PATCH 4/7] " Peng Sun
2016-09-17  2:05 ` [PATCH 5/7] " Peng Sun
2016-09-17  2:05 ` [PATCH 6/7] " Peng Sun
2016-09-17  2:05 ` [PATCH 7/7] " Peng Sun
2016-09-17  8:30   ` Greg KH
2016-09-17  8:30 ` 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=20160917083015.GA16671@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=charrer@alacritech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liodot@gmail.com \
    --cc=sironhide0null@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 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.