public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Joey Lee <jlee@novell.com>
Cc: axel.lin@gmail.com, mzxreary@0pointer.de,
	rpurdie@linux.intel.com, mjg@redhat.com, gregkh@suse.de,
	linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] msi-laptop: make struct rfkill_ops const
Date: Thu, 8 Jul 2010 11:39:03 -0700	[thread overview]
Message-ID: <20100708183903.GD31823@kroah.com> (raw)
In-Reply-To: <4C369D2B020000230001CA27@novprvlin0050.provo.novell.com>

On Thu, Jul 08, 2010 at 11:53:15AM -0600, Joey Lee wrote:
> Hi Axel, 
> 
> 於 四,2010-07-08 於 10:08 +0800,Axel Lin 提到:
> > rfkill uses a const struct rfkill_ops pointer.
> > 
> > Signed-off-by: Axel Lin <axel.lin@gmail.com>
> > ---
> >  drivers/platform/x86/msi-laptop.c |    6 +++---
> >  1 files changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/platform/x86/msi-laptop.c b/drivers/platform/x86/msi-laptop.c
> > index afd762b..05634f8 100644
> > --- a/drivers/platform/x86/msi-laptop.c
> > +++ b/drivers/platform/x86/msi-laptop.c
> > @@ -562,15 +562,15 @@ static int rfkill_threeg_set(void *data, bool blocked)
> >  	return 0;
> >  }
> >  
> > -static struct rfkill_ops rfkill_bluetooth_ops = {
> > +static const struct rfkill_ops rfkill_bluetooth_ops = {
> >  	.set_block = rfkill_bluetooth_set
> >  };
> >  
> > -static struct rfkill_ops rfkill_wlan_ops = {
> > +static const struct rfkill_ops rfkill_wlan_ops = {
> >  	.set_block = rfkill_wlan_set
> >  };
> >  
> > -static struct rfkill_ops rfkill_threeg_ops = {
> > +static const struct rfkill_ops rfkill_threeg_ops = {
> >  	.set_block = rfkill_threeg_set
> >  };
> >  
> 
> The patch good to me, do I need Signed-off it?
> How can I signed off a patch?

You can say:
	Signed-off-by: your name <your_email>

and then Matthew will add it.

Or you can take the original patch, add your signed-off-by, and resend
it to Matthew keeping the correct authorship information there by making
sure the first line in the body of the email has:
	From: Original author <email>

so git will get it right.

hope this helps,

greg k-h

  reply	other threads:[~2010-07-08 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 17:53 [PATCH] msi-laptop: make struct rfkill_ops const Joey Lee
2010-07-08 18:39 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-07-09 10:26 Joey Lee
2010-07-09 10:24 Joey Lee
2010-07-08  2:08 Axel Lin

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=20100708183903.GD31823@kroah.com \
    --to=greg@kroah.com \
    --cc=axel.lin@gmail.com \
    --cc=gregkh@suse.de \
    --cc=jlee@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=mzxreary@0pointer.de \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rpurdie@linux.intel.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