From: Tillmann Heidsieck <theidsieck@leenox.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [RESEND PATCH v2] staging/wlan-ng: Fix potential buffer overflow in firmware handling
Date: Tue, 13 Oct 2015 12:58:06 +0000 [thread overview]
Message-ID: <20151013125806.GA19421@themis.lan> (raw)
In-Reply-To: <1444506976-11098-1-git-send-email-theidsieck@leenox.de>
On Mon, Oct 12, 2015 at 05:11:08PM +0530, Sudip Mukherjee wrote:
> On Mon, Oct 12, 2015 at 01:35:54PM +0200, Tillmann Heidsieck wrote:
> >
> > I must have rediscovered a problem I already fixed :-(
>
> Which tree are you using? You should be using staging-testing branch of
> the staging tree.
Thanks for pointing this out. I was in fact using the wrong branch as a
base. Can you point me in the direction of some sort of best-practice or
example work-flow on how to work with all the different trees and
branches? I always like to see how different people do things in order
to combine them and find what suits me best.
>
> regards
> sudip
regards
Tillmann
prev parent reply other threads:[~2015-10-13 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 19:56 [RESEND PATCH v2] staging/wlan-ng: Fix potential buffer overflow in firmware handling Tillmann Heidsieck
2015-10-12 11:14 ` Sudip Mukherjee
2015-10-12 11:35 ` Tillmann Heidsieck
2015-10-12 11:53 ` Sudip Mukherjee
2015-10-13 12:58 ` Tillmann Heidsieck [this message]
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=20151013125806.GA19421@themis.lan \
--to=theidsieck@leenox.de \
--cc=kernel-janitors@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.