From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>,
"Gustavo Padovan" <gustavo@padovan.org>
Cc: linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@intel.com>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] bluetooth: opcode field of sent commands is little endian.
Date: Mon, 25 Jun 2012 11:02:56 +0300 [thread overview]
Message-ID: <20120625080254.GB11001@aemeltch-MOBL1> (raw)
In-Reply-To: <1340609570.5461.50.camel@thor.local>
Hi Michel,
On Mon, Jun 25, 2012 at 09:32:50AM +0200, Michel Dänzer wrote:
> > > Also, it would have been nice if that fix was promoted to stable, so I
> > > wouldn't have had to spend a good part of the weekend bisecting...
> >
> > Thinks like this happen. However after you bisected the issue you could
> > have just checked what is in Linus' or bluetooth-next tree.
>
> You're probably right. It just didn't occur to me that someone would
> have fixed this but not forwarded the fix to stable, because I generally
> do that. :}
Sorry for that, this and bunch of other fixes for byte order bugs needs to
be promoted to stable.
> Will you submit the fix to stable, or should I?
I added Gustavo to CC as he usually makes pull requests.
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-06-25 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 6:38 [PATCH] bluetooth: opcode field of sent commands is little endian Michel Dänzer
2012-06-25 6:51 ` Marcel Holtmann
2012-06-25 7:06 ` Michel Dänzer
2012-06-25 7:22 ` Marcel Holtmann
2012-06-25 7:32 ` Michel Dänzer
2012-06-25 8:02 ` Andrei Emeltchenko [this message]
2012-06-25 9:20 ` David Laight
2012-06-25 9:33 ` Michel Dänzer
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=20120625080254.GB11001@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=marcel@holtmann.org \
--cc=michel@daenzer.net \
/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