All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wong, Joshua Weng Onn" <joshua.weng.onn.wong@intel.com>
To: Alexander Aring <aar@pengutronix.de>
Cc: "alex.aring@gmail.com" <alex.aring@gmail.com>,
	"jukka.rissanen@linux.intel.com" <jukka.rissanen@linux.intel.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: RE: Bluetooth 6lowpan ping6 slab corruption
Date: Mon, 19 Dec 2016 00:27:14 +0000	[thread overview]
Message-ID: <E3B98393E6037849B63EA428240A65135C42A6@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <efdc1a54-7fdc-80b8-f46d-d663addae509@pengutronix.de>

Hi Alex,

> Hi,
> 
> On 12/16/2016 09:18 AM, Wong, Joshua Weng Onn wrote:
> ...
> >
> > Thank you for informing me about this. Sorry as I was not aware of the newer
> patches that you submitted to mainline.
> > At the moment I am not able to upgrade the kernel to a recent version as the
> other teams in my department are using kernel version 4.1.27 and I have to
> follow it strictly.
> >
> > I just got an idea. Perhaps what I can do is backport the patches and apply
> them to this version of the kernel. I am not sure if it will work entirely. I'll discuss
> this with my lead first if he wants me to do this and let you know if I am pursuing
> this.
> >
> 
> You can backport it, yes... but please _please_ don't do it... bring it mainline and
> then backport it.
> 
> Tell that your lead as suggestion from me.
> 
> It makes no sense that you backporting it only for you. This thing need to be
> fixed upstream...
> 
> In my opinion, all people who backporting it will do work for nothing...
> The next guy/girl which wants to try that out runs again into such issues.
> 
> These patches was sending to bluetooth-next, now I am busy with other things
> and can work on it at end of April maybe... and I think only in my free-time. This
> patch-series just needs a little cleanup and send as PATCH...
> 
> - Alex

I've finally just learned how to add inline '>' characters to the previous email. Had to make some changes in my email settings.

Thank you very much for your reply.
Ok noted on that. My most sincere apologies as I am quite new to this and I am still trying to understand how open source works. Didn't realize that it will cause repetitive work for others.

I will discuss this with my technical lead and update you along the way.

Thank you.

Best regards,
Joshua

  reply	other threads:[~2016-12-19  0:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16  6:46 Bluetooth 6lowpan ping6 slab corruption Wong, Joshua Weng Onn
2016-12-16  7:44 ` Alexander Aring
2016-12-16  7:44   ` Alexander Aring
2016-12-16  8:18   ` Wong, Joshua Weng Onn
2016-12-16  9:54     ` Alexander Aring
2016-12-19  0:27       ` Wong, Joshua Weng Onn [this message]
     [not found]         ` <CAAK7Ti_wdFr6PUGzE0aDdUMTNJtNVZxRpJ7WWrV61btWcYHJJw@mail.gmail.com>
2016-12-19  6:38           ` Wong, Joshua Weng Onn
2016-12-19  8:19             ` Alexander Aring
2016-12-21 23:38         ` Wong, Joshua Weng Onn
2017-01-05  9:37           ` Alexander Aring
2017-01-05 12:57             ` Wong, Joshua Weng Onn
2016-12-16 12:34 ` Luiz Augusto von Dentz
2016-12-19  0:30   ` Wong, Joshua Weng Onn

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=E3B98393E6037849B63EA428240A65135C42A6@PGSMSX103.gar.corp.intel.com \
    --to=joshua.weng.onn.wong@intel.com \
    --cc=aar@pengutronix.de \
    --cc=alex.aring@gmail.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    /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.