From: David Miller <davem@davemloft.net>
To: petkovbb@googlemail.com
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 12:41:50 -0700 (PDT) [thread overview]
Message-ID: <20090715.124150.120992830.davem@davemloft.net> (raw)
In-Reply-To: <20090715184350.GA13708@liondog.tnic>
From: Borislav Petkov <petkovbb@googlemail.com>
Date: Wed, 15 Jul 2009 20:43:50 +0200
> 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.
Your PFX patch has no effect at all, it's just cleanup noise.
The other patch moves the debug mask from one place to another,
why can't the debug selections bet set properly as is?
next prev parent reply other threads:[~2009-07-15 19:41 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
2009-07-15 19:41 ` David Miller [this message]
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=20090715.124150.120992830.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@googlemail.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
all inboxes | Powered by JetHome®