From: Christoffer Holmstedt <christoffer@christofferholmstedt.se>
To: Varka Bhadram <varkabhadram@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: nl802154 enum misspelled, just send patch?
Date: Wed, 10 Jun 2015 10:41:44 +0200 [thread overview]
Message-ID: <20150610084144.GB20831@arazu> (raw)
In-Reply-To: <5577F5A0.9050100@gmail.com>
On Wed, Jun 10, 2015 at 02:00:24PM +0530, Varka Bhadram wrote:
> On 06/10/2015 01:54 PM, Christoffer Holmstedt wrote:
>
> >Hi
> >While working on the CCA improvements to wpan-tools I noticed that one of the
> >enums has a value misspelled. As the header is not in UAPI yet I suggest we
> >fix this.
> >
> >NL802154_CCA_UWB_MULTIPEXED is missing an l (ell) in multiplexed.
> >
> >The header file is included in wpan-tools repository and available in the
> >kernel. Should I just send a patch for bluetooth-next and then the new header
> >file is copied over to wpan-tools repository or what is the procedure here?
> >
> >I assume normal procedure for more "stable" user-space software is that the
> >kernel header file(s) should not be included in the user-space tool but instead
> >included and linked against the kernel headers (from running system or similiar
> >source). At the moment the nl802154 header is included in wpan-tools to make it
> >easier to build while developing.
> >
> >So, should I send a patch for both bluetooth-next and wpan-tools or just
> >bluetooth-next?
>
> Send patch for both trees . :-)
>
> --
> Varka Bhadram
Will do.
--
Christoffer Holmstedt
next prev parent reply other threads:[~2015-06-10 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:24 nl802154 enum misspelled, just send patch? Christoffer Holmstedt
2015-06-10 8:30 ` Varka Bhadram
2015-06-10 8:41 ` Christoffer Holmstedt [this message]
2015-06-10 8:44 ` Alexander Aring
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=20150610084144.GB20831@arazu \
--to=christoffer@christofferholmstedt.se \
--cc=linux-wpan@vger.kernel.org \
--cc=varkabhadram@gmail.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