From: Borislav Petkov <petkovbb@googlemail.com>
To: David Miller <davem@davemloft.net>
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] ide-tape: misc stuff
Date: Wed, 15 Jul 2009 20:43:50 +0200 [thread overview]
Message-ID: <20090715184350.GA13708@liondog.tnic> (raw)
In-Reply-To: <20090715.111606.193724419.davem@davemloft.net>
On Wed, Jul 15, 2009 at 11:16:06AM -0700, David Miller wrote:
> From: Borislav Petkov <petkovbb@googlemail.com>
> Date: Wed, 15 Jul 2009 17:18:16 +0200
>
> > here is some ide-tape stuff.
> >
> > * 0001: somehow fell through the cracks, DEBUG build fix
>
> This is OK.
>
> > * 0002: mostly code unification
>
> I'm not applying this. IDE is in deep maintainence mode and
> we really need to avoid changes that don't fix real bugs and
> have only marginal benefit, like this change.
>
> > * 0003: this one converts ide-tape to the debugging scheme we use with ide-cd
> > and ide-floppy. It adds some debug calls at important places and has proven
> > very helpful when working on bug reports with users. No functional change.
>
> I'm not applying this for the same reason as patch #2.
Well, the downside to that is whenever there's a bug report and I want
the user to do a debug build and send me the output, I'll have to rehash
that debug patch and send it to her/him, maybe teach her/him how to
patch a kernel, build it and catch the output and send it my way before
we do some real work. Having the change upstream makes it _a_ _lot_
_more_ easier to do that and this is experience talking, we had several
scenarious like that already.
So, applying those would be of great help to me without the danger of
introducing any regressions but I guess, it's your call. Still, I'd
really appreciate it if you reconsidered.
Thanks.
> > * 0004: real bugfix
>
> Ok, did you test this?
Yes.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2009-07-15 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 15:18 Borislav Petkov
2009-07-15 15:18 ` [PATCH 1/4] ide-tape: fix debug call Borislav Petkov
2009-07-15 15:18 ` [PATCH 2/4] ide-tape: use PFX to all printks Borislav Petkov
2009-07-15 15:18 ` [PATCH 3/4] ide-tape: convert to ide_debug_log macro Borislav Petkov
2009-07-15 15:18 ` [PATCH 4/4] ide-tape: fix handling of postponed rqs Borislav Petkov
2009-07-15 18:16 ` [PATCH 0/4] ide-tape: misc stuff David Miller
2009-07-15 18:43 ` Borislav Petkov [this message]
2009-07-15 19:41 ` David Miller
2009-07-16 6:52 ` Borislav Petkov
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=20090715184350.GA13708@liondog.tnic \
--to=petkovbb@googlemail.com \
--cc=bzolnier@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®