From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Gustavo Padovan <gustavo@padovan.org>,
Szymon Janc <szymon.janc@tieto.com>,
linux-bluetooth@vger.kernel.org, kanak.gupta@stericsson.com
Subject: Re: [PATCH 2/2] Bluetooth: mgmt: Don't allow to set invalid value to DeviceID source
Date: Fri, 16 Mar 2012 09:20:43 -0700 [thread overview]
Message-ID: <1331914843.14217.160.camel@aeonflux> (raw)
In-Reply-To: <20120316161310.GC22160@x220>
Hi Johan,
> > > Reply with MGMT_STATUS_INVALID_PARAMS when userspace is trying to set
> > > source with out-of-scope value.
> > >
> > > Signed-off-by: Szymon Janc <szymon.janc@tieto.com>
> > > ---
> > > net/bluetooth/mgmt.c | 9 ++++++++-
> > > 1 file changed, 8 insertions(+), 1 deletion(-)
> >
> > This one should go to bluetooth.git first.
> >
> > Acked-by: Gustavo Padovan <gustavo@padovan.org>
>
> I went ahead and applied both directly to my bluetooth-next tree. I
> don't think this one is critical enough to deserve to go to
> bluetooth.git.
you are both kidding me here right now, right? Of course this is not
going into bluetooth.git since it is not even in net-next or scheduled
for the next merge window.
And nothing goes into bluetooth.git first (unless it only applies
there). Everything goes into bluetooth-next.git first.
Regards
Marcel
next prev parent reply other threads:[~2012-03-16 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 15:02 [PATCH 1/2] Bluetooth: mgmt: Fix some code style and indentation issues Szymon Janc
2012-03-16 15:02 ` [PATCH 2/2] Bluetooth: mgmt: Don't allow to set invalid value to DeviceID source Szymon Janc
2012-03-16 15:06 ` Gustavo Padovan
2012-03-16 16:11 ` Marcel Holtmann
2012-03-16 16:13 ` Johan Hedberg
2012-03-16 16:20 ` Marcel Holtmann [this message]
2012-03-16 16:31 ` Johan Hedberg
2012-03-16 16:10 ` Marcel Holtmann
2012-03-16 15:05 ` [PATCH 1/2] Bluetooth: mgmt: Fix some code style and indentation issues Gustavo Padovan
2012-03-16 16:09 ` Marcel Holtmann
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=1331914843.14217.160.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=kanak.gupta@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@tieto.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;
as well as URLs for NNTP newsgroup(s).