All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Janakiram Sistla <janakiram.sistla@gmail.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] Adding kerneldoc entry for radio type GPS
Date: Wed, 18 Nov 2009 17:05:10 +0100	[thread overview]
Message-ID: <1258560310.2003.91.camel@violet> (raw)
In-Reply-To: <4fb5db50911180755u4e01814bvcc4d0ec8d396abd@mail.gmail.com>

Hi Janakiram,

> >>
> >> diff --git a/include/linux/rfkill.h b/include/linux/rfkill.h
> >> index d787d5f..212f555 100644
> >> --- a/include/linux/rfkill.h
> >> +++ b/include/linux/rfkill.h
> >> @@ -36,6 +36,7 @@
> >>   * @RFKILL_TYPE_WIMAX: switch is on a WiMAX device.
> >>   * @RFKILL_TYPE_WWAN: switch is on a wireless WAN device.
> >>   * @RFKILL_TYPE_FM: switch is on a FM device.
> >> + * @RFKILL_TYPE_GPS: switch is on a GPS device.
> >>   * @NUM_RFKILL_TYPES: number of defined rfkill types
> >>   */
> >>  enum rfkill_type {
> >
> > so this is getting stupid right now. I am sick of a really simple patch
> > causes so much trouble. Even this one is wrong again. The GPS doc should
> > obviously before FM.
> Marcel I think you want me to submit GPS doc patch first.I will be
> doing it shortly and then i will do it for FM.I am sorry for this mis
> understanding

I don't care in which order you submit the patches, but the order of the
documentation should match the order in the enum. That is not a strict
requirement, but here it makes total sense to do so.

Also don't worry with the patches anymore. This took way too much ping
pong to get it right, that I just wrote them by myself and submitted
them for inclusion.

Regards

Marcel



  reply	other threads:[~2009-11-18 16:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 15:22 [PATCH 2/2] Adding kerneldoc entry for radio type GPS janakiram.sistla
2009-11-18 15:35 ` Marcel Holtmann
2009-11-18 15:55   ` Janakiram Sistla
2009-11-18 16:05     ` Marcel Holtmann [this message]
2009-11-18 16:22       ` Janakiram Sistla
2009-11-18 17:04       ` Janakiram Sistla
2009-11-18 17:26       ` Janakiram Sistla
  -- strict thread matches above, loose matches on Subject: below --
2009-11-18 15:56 janakiram.sistla

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=1258560310.2003.91.camel@violet \
    --to=marcel@holtmann.org \
    --cc=janakiram.sistla@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.