linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] staging: sm750fb: fix improper typedef usage
Date: Sun, 30 Aug 2015 07:15:00 +0000	[thread overview]
Message-ID: <20150830070300.GA2896@fool> (raw)
In-Reply-To: <20150819022745.GA5960@brian_archtop.Home>

On Sat, Aug 29, 2015 at 05:58:50PM -0400, Brian Stottler wrote:
> On Thu, Aug 27, 2015 at 05:41:42PM +0530, Sudip Mukherjee wrote:
> > I think you need to update your tree. This patch will not apply due to
> > changes already done in some of the files.
> 
> My mistake, thanks for the heads up. I will resubmit my corrected patch as soon
> as possible. Just to clarify, the tree in question is torvalds/linux.git,
> correct?
No, use Greg's staging-testing tree.

regards
sudip

      parent reply	other threads:[~2015-08-30  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  2:27 [PATCH] staging: sm750fb: fix improper typedef usage Brian Stottler
2015-08-27 12:23 ` Sudip Mukherjee
2015-08-29 21:58 ` Brian Stottler
2015-08-30  7:15 ` Sudip Mukherjee [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=20150830070300.GA2896@fool \
    --to=sudipm.mukherjee@gmail.com \
    --cc=linux-fbdev@vger.kernel.org \
    /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).