All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Parmeshwr Prasad <parmeshwr_prasad@dell.com>,
	Joe Perches <joe@perches.com>,
	"plagnioj@jcrosoft.com" <plagnioj@jcrosoft.com>,
	"tomi.valkeinen@ti.com" <tomi.valkeinen@ti.com>,
	"trivial@kernel.org" <trivial@kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2]Trivial patch: to solve indentation warnings in amba-clcd.c driver
Date: Sat, 14 Feb 2015 10:20:58 +0000	[thread overview]
Message-ID: <20150214100858.GB8946@sudip-PC> (raw)
In-Reply-To: <20150213133618.GZ8656@n2100.arm.linux.org.uk>

On Fri, Feb 13, 2015 at 01:36:18PM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 13, 2015 at 08:28:10AM -0500, Parmeshwr Prasad wrote:
> > 
> > This is second patch in series.
> > In driver in_atomic we should not use to check if code is unning in IRQ.
> > clcdfb_sleep() function is used to give some delay between operation.
> > I have used schedule_timeout() function for same amount of delay.
> 
> Frankly, this patch is a mess.  It seems to contain unrelated changes.
and this patch is corrupted. your commit message is a mess and the maintainer has to edit it by hand before applying.
if i remember correctly you have been told multiple times by many people to fix your commit message.
and try to use git send-email to send your patches.

regards
sudip


> 
> Please always review your own patches before you send them - this will
> allow you to catch such errors before you post them publically.
> 
> The change to clcdfb_sleep() is wrong in any case - you will end up
> calling schedule_timeout() from illegal contexts (eg, when the
> framebuffer gets blanked/unblanked.)
> 
> -- 

WARNING: multiple messages have this Message-ID (diff)
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Parmeshwr Prasad <parmeshwr_prasad@dell.com>,
	Joe Perches <joe@perches.com>,
	"plagnioj@jcrosoft.com" <plagnioj@jcrosoft.com>,
	"tomi.valkeinen@ti.com" <tomi.valkeinen@ti.com>,
	"trivial@kernel.org" <trivial@kernel.org>,
	"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2]Trivial patch: to solve indentation warnings in amba-clcd.c driver
Date: Sat, 14 Feb 2015 15:38:58 +0530	[thread overview]
Message-ID: <20150214100858.GB8946@sudip-PC> (raw)
In-Reply-To: <20150213133618.GZ8656@n2100.arm.linux.org.uk>

On Fri, Feb 13, 2015 at 01:36:18PM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 13, 2015 at 08:28:10AM -0500, Parmeshwr Prasad wrote:
> > 
> > This is second patch in series.
> > In driver in_atomic we should not use to check if code is unning in IRQ.
> > clcdfb_sleep() function is used to give some delay between operation.
> > I have used schedule_timeout() function for same amount of delay.
> 
> Frankly, this patch is a mess.  It seems to contain unrelated changes.
and this patch is corrupted. your commit message is a mess and the maintainer has to edit it by hand before applying.
if i remember correctly you have been told multiple times by many people to fix your commit message.
and try to use git send-email to send your patches.

regards
sudip


> 
> Please always review your own patches before you send them - this will
> allow you to catch such errors before you post them publically.
> 
> The change to clcdfb_sleep() is wrong in any case - you will end up
> calling schedule_timeout() from illegal contexts (eg, when the
> framebuffer gets blanked/unblanked.)
> 
> -- 

  reply	other threads:[~2015-02-14 10:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 11:21 [PATCH 1/2]Trivial patch: to solve indentation warnings in amba-clcd.c driver Parmeshwr Prasad
2015-02-13 11:21 ` Parmeshwr Prasad
2015-02-13 11:35 ` Russell King - ARM Linux
2015-02-13 11:59   ` Joe Perches
2015-02-13 11:59     ` Joe Perches
2015-02-13 12:03     ` Russell King - ARM Linux
2015-02-13 12:03       ` Russell King - ARM Linux
2015-02-13 13:28     ` [PATCH 2/2]Trivial " Parmeshwr Prasad
2015-02-13 13:28       ` Parmeshwr Prasad
2015-02-13 13:36       ` Russell King - ARM Linux
2015-02-14 10:08         ` Sudip Mukherjee [this message]
2015-02-14 10:20           ` 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=20150214100858.GB8946@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=parmeshwr_prasad@dell.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=tomi.valkeinen@ti.com \
    --cc=trivial@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 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.