From: Dan Carpenter <dan.carpenter@oracle.com>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
Teddy Wang <teddy.wang@siliconmotion.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH RESEND 2 1/5] staging: sm750fb: Use memset_io instead of memset
Date: Mon, 23 Mar 2015 11:51:29 +0000 [thread overview]
Message-ID: <20150323115129.GI10964@mwanda> (raw)
In-Reply-To: <CAA5enKaPnRBT=8Tkx7rm6GQYXMvA=pwxmRYpnkRU8uHok8ypUg@mail.gmail.com>
Oh hm... This is an actual RESEND patch.
RESEND is a flag to show a mess up in the system. I like to take a look
at those to see what went wrong. The process failure was that you
messed up the threading earlier. Take a look at the --in-reply-to flag.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
Teddy Wang <teddy.wang@siliconmotion.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Subject: Re: [PATCH RESEND 2 1/5] staging: sm750fb: Use memset_io instead of memset
Date: Mon, 23 Mar 2015 14:51:29 +0300 [thread overview]
Message-ID: <20150323115129.GI10964@mwanda> (raw)
In-Reply-To: <CAA5enKaPnRBT=8Tkx7rm6GQYXMvA=pwxmRYpnkRU8uHok8ypUg@mail.gmail.com>
Oh hm... This is an actual RESEND patch.
RESEND is a flag to show a mess up in the system. I like to take a look
at those to see what went wrong. The process failure was that you
messed up the threading earlier. Take a look at the --in-reply-to flag.
regards,
dan carpenter
next prev parent reply other threads:[~2015-03-23 11:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 15:22 [PATCH RESEND 2 1/5] staging: sm750fb: Use memset_io instead of memset Lorenzo Stoakes
2015-03-20 15:22 ` [PATCH RESEND 2 2/5] staging: sm750fb: Make internal functions static Lorenzo Stoakes
2015-03-20 15:22 ` [PATCH RESEND 2 3/5] staging: sm750fb: Remove unused function Lorenzo Stoakes
2015-03-20 15:22 ` Lorenzo Stoakes
2015-03-20 15:22 ` [PATCH RESEND 2 4/5] staging: sm750fb: Fix __iomem pointer types Lorenzo Stoakes
2015-03-20 15:22 ` [PATCH RESEND 2 5/5] staging: sm750fb: Remove spinlock helper function Lorenzo Stoakes
2015-03-20 15:22 ` Lorenzo Stoakes
2015-03-23 10:53 ` [PATCH RESEND 2 1/5] staging: sm750fb: Use memset_io instead of memset Dan Carpenter
2015-03-23 10:53 ` Dan Carpenter
2015-03-23 11:14 ` Lorenzo Stoakes
2015-03-23 11:51 ` Dan Carpenter [this message]
2015-03-23 11:51 ` Dan Carpenter
2015-03-23 12:43 ` Lorenzo Stoakes
2015-03-23 12:55 ` Sudip Mukherjee
2015-03-23 12:55 ` Sudip Mukherjee
2015-03-23 13:02 ` Lorenzo Stoakes
2015-03-23 13:14 ` Sudip Mukherjee
2015-03-23 13:26 ` Sudip Mukherjee
2015-03-23 13:16 ` Lorenzo Stoakes
2015-03-23 13:21 ` Lorenzo Stoakes
2015-03-23 13:25 ` Lorenzo Stoakes
2015-03-23 13:43 ` Sudip Mukherjee
2015-03-23 13:55 ` Sudip Mukherjee
2015-03-23 13:55 ` Sudip Mukherjee
2015-03-23 13:55 ` Sudip Mukherjee
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=20150323115129.GI10964@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lstoakes@gmail.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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.