From: Pavel Machek <pavel@suse.cz>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: netdev@oss.sgi.com, kernel list <linux-kernel@vger.kernel.org>,
jbohac@suse.cz, jbenc@suse.cz
Subject: Re: ipw2100: intrusive cleanups, working this time ;-)
Date: Fri, 13 May 2005 12:01:18 +0200 [thread overview]
Message-ID: <20050513100118.GG1780@elf.ucw.cz> (raw)
In-Reply-To: <4283FA4D.3010208@linux.intel.com>
Hi!
> >There's a lot to clean up in header file, too... And this time it
> >actually works.
> >
> >Now, I'd like to clean it a bit more and then submit it to akpm for
> >-mm series. Will someone hate me for doing that?
> >
> >
> Initial look over the patch looks reasonable; no functionality changes,
> just code reduction. That said, I would like to pass it through a quick
> validation cycle before its picked up.
>
> We submitted ipw2100-1.1.0 to netdev a month or so ago. I would like to
> see it go in to -mm through the netdev tree. I'll ask our QA folks to
> run this patch through a quick regression cycle here just to do a sanity
> check on it. Assuming nothing comes up, and if Jeff hasn't merged the
> ipw2100 code yet, I'll resubmit the ipw2100 driver w/ your patch applied.
Ok. [I may try and do more similar cleanups soon.]
> Part of the process we have in place is to try and make sure that the
> versions that get picked up by distros and the majority of users have a
> 'known' level of quality. As part of that, we only want to get changes
> pushed to -mm and eventual mainline that have gone through regression
> testing.
>
> Sound workable?
Yes... Maybe it would be better to have regression testing between -mm
and mainline. I.e. allow "good looking" changes go to -mm, so that -mm
tree gets nice, small patches, but only dump changes from -mm to
-linus when it actually works.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
next prev parent reply other threads:[~2005-05-13 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 22:50 ipw2100: intrusive cleanups, working this time ;-) Pavel Machek
2005-05-13 0:52 ` James Ketrenos
2005-05-13 3:42 ` Greg KH
2005-05-13 6:25 ` James Ketrenos
2005-05-13 16:48 ` Greg KH
2005-05-13 8:21 ` Christoph Hellwig
2005-05-13 10:01 ` Pavel Machek [this message]
2005-05-13 8:36 ` Denis Vlasenko
2005-05-13 9:41 ` Pavel Machek
2005-05-13 11:54 ` John M Flinchbaugh
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=20050513100118.GG1780@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=jbenc@suse.cz \
--cc=jbohac@suse.cz \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).