From: Greg KH <gregkh@linuxfoundation.org>
To: Jandy Gou <gouqingsong@goodix.com>
Cc: thomas.petazzoni@free-electrons.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix the sparse warning: drivers/staging/fbtft/fbtft-io.c:74:29: warning: incorrect type in assignment (different base types) drivers/staging/fbtft/fbtft-io.c:74:29: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident> drivers/staging/fbtft/fbtft-io.c:74:29: got restricted __be64 [usertype] <noident>
Date: Tue, 16 May 2017 10:00:47 +0200 [thread overview]
Message-ID: <20170516080047.GB4701@kroah.com> (raw)
In-Reply-To: <1494920547-11782-2-git-send-email-gouqingsong@goodix.com>
On Tue, May 16, 2017 at 03:42:27PM +0800, Jandy Gou wrote:
> Signed-off-by: Jandy Gou <gouqingsong@goodix.com>
Your subject is a bit messed up :(
Please fix and resend.
No need for the 0/1 email for just a single patch.
thanks,
greg k-h
next prev parent reply other threads:[~2017-05-16 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 7:42 [PATCH] staging: fbtft: fix sparse warning Jandy Gou
2017-05-16 7:42 ` [PATCH] fix the sparse warning: drivers/staging/fbtft/fbtft-io.c:74:29: warning: incorrect type in assignment (different base types) drivers/staging/fbtft/fbtft-io.c:74:29: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident> drivers/staging/fbtft/fbtft-io.c:74:29: got restricted __be64 [usertype] <noident> Jandy Gou
2017-05-16 8:00 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-16 7:09 Jandy Gou
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=20170516080047.GB4701@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gouqingsong@goodix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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
Powered by JetHome