From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
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
Subject: Re: [PATCH RESEND 2 1/5] staging: sm750fb: Use memset_io instead of memset
Date: Mon, 23 Mar 2015 13:55:11 +0000 [thread overview]
Message-ID: <20150323133048.GA27897@sudip-PC> (raw)
In-Reply-To: <CAA5enKYeq8id8s+w+AA1e0haZci9ZEXj+3VSPdm_=Uy7vbHOFQ@mail.gmail.com>
On Mon, Mar 23, 2015 at 01:25:37PM +0000, Lorenzo Stoakes wrote:
> On 23 March 2015 at 13:21, Lorenzo Stoakes <lstoakes@gmail.com> wrote:
> > Sigh. Checking the emails I actually sent, I seem to *somehow* have
> > sent old files in this resend :S I really don't know how this
> > happened. My copies of the patches all apply perfectly correctly, but
> > these are not the ones I sent.
>
> And just to add to my embarrassment, this is actually *not* the case,
> they DO all apply, gmail mangled the patches. So they seem fine after
> all!
>
> Sudip - could you try to carefully grab each of the 5 patches with
> [RESEND 2] in the subject to make sure you are applying them
> correctly?
my apologies. they are applying properly. i had them already applied
for testing that hardware change, and again i tried to apply them.
sorry for the confusion. :(
regards
sudip
>
> Best,
>
> --
> Lorenzo Stoakes
> https:/ljs.io
next prev parent reply other threads:[~2015-03-23 13:55 UTC|newest]
Thread overview: 17+ 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 ` [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-23 10:53 ` [PATCH RESEND 2 1/5] staging: sm750fb: Use memset_io instead of memset Dan Carpenter
2015-03-23 11:14 ` Lorenzo Stoakes
2015-03-23 11:51 ` Dan Carpenter
2015-03-23 12:43 ` Lorenzo Stoakes
2015-03-23 12:55 ` Sudip Mukherjee
2015-03-23 13:02 ` Lorenzo Stoakes
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:55 ` Sudip Mukherjee [this message]
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=20150323133048.GA27897@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=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=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 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).