From: Marcelo Tosatti <mtosatti@redhat.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Benjamin Cherian <benjamin.cherian.kernel@gmail.com>,
Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, marcelo@kvack.org
Subject: Re: Bug with USB proc_bulk in 2.4 kernel
Date: Fri, 11 Aug 2006 21:14:57 -0300 [thread overview]
Message-ID: <20060812001457.GA2676@dmt> (raw)
In-Reply-To: <20060809170201.GA25530@1wt.eu>
On Wed, Aug 09, 2006 at 07:02:01PM +0200, Willy Tarreau wrote:
> Hi Benjamin,
>
> On Wed, Aug 09, 2006 at 10:01:41AM -0700, Benjamin Cherian wrote:
> > Willy,
> > Sorry I didn't notice your email till now.
>
> no problem.
>
> > On Friday 04 August 2006 09:55, Willy Tarreau wrote:
> > > The problem is that Marcelo is very very busy those days (as you might have
> > > noticed from the delay between each release), and there are a good bunch of
> > > security fixes in -rc3 which should wait too much in -rc. Maybe an -rc4
> > > would be OK, but I don't know if Marcelo has enough time to spend on yet
> > > another RC. Otherwise, if I produce a 2.4.34-pre1 about one week after
> > > 2.4.33, does that fit your needs ? I already have a few fixes waiting which
> > > might be worth a first pre-release.
> >
> > It would be nice if you could do another rc, because otherwise it seems the
> > patch wouldn't get into a stable kernel for a long time. But if it's really
> > too much work for Marcelo, I would understand you putting it in th 2.4.34
> > pre-release.
>
> The real problem is that Marcelo seems to be *very* busy. I failed to get
> any contact from him from one week now. It's even becoming worrying, I hope
> he's alright. I don't know how much time it would take him to produce another
> release, but it will for sure delay 2.4.33 for a few weeks during which Marcelo
> will still be bound to this time-consuming task. It's left to him to decide
> anyway. In normal ciscumstances, I would for sure add another -rc, but delays
> get stretched too far given the number of vulnerabilities fixed in 2.4.33.
The reason for so much delay was a serious accident which resulted in 2
weeks of hospitalization with no Internet connnectivity (and no mental
state for work).
Sorry about that.
next prev parent reply other threads:[~2006-08-12 0:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1152332281.24203.linux-kernel2news@redhat.com>
2006-07-08 20:28 ` Bug with USB proc_bulk in 2.4 kernel and possibly bug in proc_ioctl in 2.6 Pete Zaitcev
2006-07-10 19:58 ` Bug with USB proc_bulk in 2.4 kernel Benjamin Cherian
2006-07-10 20:40 ` Pete Zaitcev
2006-07-17 21:35 ` Benjamin Cherian
2006-07-17 22:19 ` Pete Zaitcev
2006-07-18 17:04 ` Benjamin Cherian
2006-07-19 1:33 ` Pete Zaitcev
2006-07-20 17:43 ` Benjamin Cherian
2006-07-25 6:07 ` Pete Zaitcev
2006-07-25 19:31 ` Willy Tarreau
2006-07-27 22:21 ` Benjamin Cherian
2006-07-27 23:49 ` Pete Zaitcev
2006-07-28 17:37 ` Benjamin Cherian
2006-07-30 7:35 ` Pete Zaitcev
2006-07-31 18:41 ` Benjamin Cherian
2006-08-02 19:51 ` Willy Tarreau
2006-08-03 1:02 ` Pete Zaitcev
2006-08-03 2:33 ` Willy Tarreau
2006-08-03 6:00 ` Pete Zaitcev
2006-08-03 6:29 ` Willy Tarreau
2006-08-04 16:57 ` Benjamin Cherian
2006-08-04 16:55 ` Willy Tarreau
2006-08-09 17:01 ` Benjamin Cherian
2006-08-09 17:02 ` Willy Tarreau
2006-08-12 0:14 ` Marcelo Tosatti [this message]
2006-08-12 3:21 ` Willy Tarreau
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=20060812001457.GA2676@dmt \
--to=mtosatti@redhat.com \
--cc=benjamin.cherian.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=marcelo@kvack.org \
--cc=w@1wt.eu \
--cc=zaitcev@redhat.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