From: Greg KH <gregkh@suse.de>
To: Kashyap Gada <gada.kashyap@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
devel@driverdev.osuosl.org, bringert@android.com,
linux-kernel@vger.kernel.org, arve@android.com,
john.stultz@linaro.org, ccross@android.com
Subject: Re: [PATCH 4/4] Staging: android: Fix struct definitioni warning from static to const
Date: Sat, 21 Jan 2012 07:53:14 -0500 [thread overview]
Message-ID: <20120121125314.GC18829@suse.de> (raw)
In-Reply-To: <20120121080838.GK3294@mwanda>
On Sat, Jan 21, 2012 at 11:08:38AM +0300, Dan Carpenter wrote:
> On Sat, Jan 21, 2012 at 02:17:49AM +0000, Kashyap Gada wrote:
> > ---
> > drivers/staging/android/ashmem.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
> > index 4a00174a5..9f1f27e 100644
> > --- a/drivers/staging/android/ashmem.c
> > +++ b/drivers/staging/android/ashmem.c
> > @@ -680,7 +680,7 @@ static long ashmem_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
> > return ret;
> > }
> >
> > -const struct file_operations ashmem_fops = {
> > +static const struct file_operations ashmem_fops = {
> > .owner = THIS_MODULE,
> > .open = ashmem_open,
> > .release = ashmem_release,
>
> No. We're not going to merge the broken patch which removes the
> static.
>
> Plus your patch numbering is totally bogus.
> [PATCH 2/2]
> [PATCH 3/3]
> [PATCH 4/4]
> [PATCH 5/5]
>
> The second number is supposed to say how many patches there are in
> the series. If these were bug fixes, we'd go out of our way to work
> with you, but you're just sending random whitespace fixes so they
> have to be pretty much perfect. (In other words, please slow down
> and work more carefully or else focus on fixing bugs instead of
> whitespace).
The patches also don't have the most basic things needed for acceptance
(i.e. a description and most importantly, a Signed-off-by:), so I can't
take them at all.
greg k-h
next prev parent reply other threads:[~2012-01-21 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 2:17 Kashyap Gada
2012-01-21 8:08 ` Dan Carpenter
2012-01-21 12:53 ` Greg KH [this message]
[not found] ` <CANJXcUaxX8kTArQ3tL4hHnOVAq=yLzLjfMe1CbSi-n-UcW6dEw@mail.gmail.com>
2012-01-21 13:45 ` Greg KH
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=20120121125314.GC18829@suse.de \
--to=gregkh@suse.de \
--cc=arve@android.com \
--cc=bringert@android.com \
--cc=ccross@android.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gada.kashyap@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@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
Powered by JetHome