All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobin Harding <me@tobin.cc>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org,
	Dmitry Eremin <dmitry.eremin@intel.com>,
	Abdul Hussain <habdul@visteon.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	James Nunez <james.a.nunez@intel.com>,
	patrik.r.jakobsson@gmail.com, linux-kernel@vger.kernel.org,
	Oleg Drokin <oleg.drokin@intel.com>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"John L. Hammond" <john.hammond@intel.com>,
	Frank Zago <fzago@cray.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH] staging: lustre: llite: kzalloc/copy_to_user to memdup_user
Date: Mon, 23 May 2016 10:20:07 +1000	[thread overview]
Message-ID: <20160523002007.GA14493@eros.local> (raw)
In-Reply-To: <20160522222538.GA17573@kroah.com>

On Sun, May 22, 2016 at 03:25:38PM -0700, Greg Kroah-Hartman wrote:
> On Mon, May 23, 2016 at 07:49:29AM +1000, Tobin C Harding wrote:
> > kzalloc call followed by copy_to_user can be replaced by call to memdup_user.
> > 
> > Signed-off-by: Tobin C Harding <me@tobin.cc>
>
> Why did you send this twice?

Because I'm a git send-email amateur.

> > ---
> >  drivers/gpu/drm/gma500/gma_display.c      |  2 +-
> >  drivers/staging/lustre/lustre/llite/dir.c | 22 +++++++---------------
> >  2 files changed, 8 insertions(+), 16 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/gma500/gma_display.c b/drivers/gpu/drm/gma500/gma_display.c
> > index 5bf765d..8a1fb25 100644
> > --- a/drivers/gpu/drm/gma500/gma_display.c
> > +++ b/drivers/gpu/drm/gma500/gma_display.c
> > @@ -285,7 +285,7 @@ void gma_crtc_dpms(struct drm_crtc *crtc, int mode)
> >  
> >             /* Wait for vblank for the disable to take effect */
> >             gma_wait_for_vblank(dev);
> > -
> > +l
>
> What?  What does this have to do with lustre?

Turns out I'm a git amateur in general, the gma_display changes should not have
been committed on this branch.

> It's kind of obvious you didn't build this :(

Epic fail.

> Please be more careful in the future.
>
> greg k-h

I am humbly attempting to learn the way of kernel dev, thank you for your
patience, I will endeavor to be more careful.

Regards,
Tobin Harding.

WARNING: multiple messages have this Message-ID (diff)
From: Tobin Harding <me@tobin.cc>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org,
	Dmitry Eremin <dmitry.eremin@intel.com>,
	Abdul Hussain <habdul@visteon.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	James Nunez <james.a.nunez@intel.com>,
	patrik.r.jakobsson@gmail.com, linux-kernel@vger.kernel.org,
	Oleg Drokin <oleg.drokin@intel.com>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"John L. Hammond" <john.hammond@intel.com>,
	Frank Zago <fzago@cray.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	lustre-devel@lists.lustre.org
Subject: Re: [PATCH] staging: lustre: llite: kzalloc/copy_to_user to memdup_user
Date: Mon, 23 May 2016 10:20:07 +1000	[thread overview]
Message-ID: <20160523002007.GA14493@eros.local> (raw)
In-Reply-To: <20160522222538.GA17573@kroah.com>

On Sun, May 22, 2016 at 03:25:38PM -0700, Greg Kroah-Hartman wrote:
> On Mon, May 23, 2016 at 07:49:29AM +1000, Tobin C Harding wrote:
> > kzalloc call followed by copy_to_user can be replaced by call to memdup_user.
> > 
> > Signed-off-by: Tobin C Harding <me@tobin.cc>
>
> Why did you send this twice?

Because I'm a git send-email amateur.

> > ---
> >  drivers/gpu/drm/gma500/gma_display.c      |  2 +-
> >  drivers/staging/lustre/lustre/llite/dir.c | 22 +++++++---------------
> >  2 files changed, 8 insertions(+), 16 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/gma500/gma_display.c b/drivers/gpu/drm/gma500/gma_display.c
> > index 5bf765d..8a1fb25 100644
> > --- a/drivers/gpu/drm/gma500/gma_display.c
> > +++ b/drivers/gpu/drm/gma500/gma_display.c
> > @@ -285,7 +285,7 @@ void gma_crtc_dpms(struct drm_crtc *crtc, int mode)
> >  
> >             /* Wait for vblank for the disable to take effect */
> >             gma_wait_for_vblank(dev);
> > -
> > +l
>
> What?  What does this have to do with lustre?

Turns out I'm a git amateur in general, the gma_display changes should not have
been committed on this branch.

> It's kind of obvious you didn't build this :(

Epic fail.

> Please be more careful in the future.
>
> greg k-h

I am humbly attempting to learn the way of kernel dev, thank you for your
patience, I will endeavor to be more careful.

Regards,
Tobin Harding.

WARNING: multiple messages have this Message-ID (diff)
From: Tobin Harding <me@tobin.cc>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: patrik.r.jakobsson@gmail.com, David Airlie <airlied@linux.ie>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	James Simmons <jsimmons@infradead.org>,
	"John L. Hammond" <john.hammond@intel.com>,
	Dmitry Eremin <dmitry.eremin@intel.com>,
	Frank Zago <fzago@cray.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Al Viro <viro@zeniv.linux.org.uk>,
	James Nunez <james.a.nunez@intel.com>,
	Abdul Hussain <habdul@visteon.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: lustre: llite: kzalloc/copy_to_user to memdup_user
Date: Mon, 23 May 2016 10:20:07 +1000	[thread overview]
Message-ID: <20160523002007.GA14493@eros.local> (raw)
In-Reply-To: <20160522222538.GA17573@kroah.com>

On Sun, May 22, 2016 at 03:25:38PM -0700, Greg Kroah-Hartman wrote:
> On Mon, May 23, 2016 at 07:49:29AM +1000, Tobin C Harding wrote:
> > kzalloc call followed by copy_to_user can be replaced by call to memdup_user.
> > 
> > Signed-off-by: Tobin C Harding <me@tobin.cc>
>
> Why did you send this twice?

Because I'm a git send-email amateur.

> > ---
> >  drivers/gpu/drm/gma500/gma_display.c      |  2 +-
> >  drivers/staging/lustre/lustre/llite/dir.c | 22 +++++++---------------
> >  2 files changed, 8 insertions(+), 16 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/gma500/gma_display.c b/drivers/gpu/drm/gma500/gma_display.c
> > index 5bf765d..8a1fb25 100644
> > --- a/drivers/gpu/drm/gma500/gma_display.c
> > +++ b/drivers/gpu/drm/gma500/gma_display.c
> > @@ -285,7 +285,7 @@ void gma_crtc_dpms(struct drm_crtc *crtc, int mode)
> >  
> >             /* Wait for vblank for the disable to take effect */
> >             gma_wait_for_vblank(dev);
> > -
> > +l
>
> What?  What does this have to do with lustre?

Turns out I'm a git amateur in general, the gma_display changes should not have
been committed on this branch.

> It's kind of obvious you didn't build this :(

Epic fail.

> Please be more careful in the future.
>
> greg k-h

I am humbly attempting to learn the way of kernel dev, thank you for your
patience, I will endeavor to be more careful.

Regards,
Tobin Harding.

  reply	other threads:[~2016-05-23  0:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-22 21:49 [lustre-devel] [PATCH] staging: lustre: llite: kzalloc/copy_to_user to memdup_user Tobin C Harding
2016-05-22 21:49 ` Tobin C Harding
2016-05-22 22:25 ` [lustre-devel] " Greg Kroah-Hartman
2016-05-22 22:25   ` Greg Kroah-Hartman
2016-05-22 22:25   ` Greg Kroah-Hartman
2016-05-23  0:20   ` Tobin Harding [this message]
2016-05-23  0:20     ` Tobin Harding
2016-05-23  0:20     ` Tobin Harding
  -- strict thread matches above, loose matches on Subject: below --
2016-05-22 21:52 [lustre-devel] " Tobin C Harding

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=20160523002007.GA14493@eros.local \
    --to=me@tobin.cc \
    --cc=Julia.Lawall@lip6.fr \
    --cc=airlied@linux.ie \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dmitry.eremin@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fzago@cray.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=habdul@visteon.com \
    --cc=james.a.nunez@intel.com \
    --cc=john.hammond@intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@intel.com \
    --cc=patrik.r.jakobsson@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.