From: Jim Duda <jim@duda.tzo.com>
To: Borislav Petkov <petkovbb@googlemail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: 2.6.31-rc1 with ide-tape / STT2000A
Date: Sun, 09 Aug 2009 18:51:56 -0400 [thread overview]
Message-ID: <4A7F530C.9090209@duda.tzo.com> (raw)
In-Reply-To: <20090809072823.GA2130@liondog.tnic>
On 08/09/2009 03:28 AM, Borislav Petkov wrote:
>
> If you'd like to test patches you can get Dave's linux-next git repo at
> http://git.kernel.org/?p=linux/kernel/git/davem/ide-next-2.6.git;a=summary
>
I don't have any experience with installing patches from the git repo.
I tried to figure it out, but didn't have much luck.
If there is a FAQ or HOWTO on git patches, I'll read it.
> apply the patch below and catch all boot output from your machine and
> send it to me.
I upgraded to rc5, and applied these patches.
I'm not getting any additional information in my kernel logs.
The rc5 source uses DEBUG_LOG and not IDETAPE_DEBUG_LOG.
Will Dave's ide-next be part of rc6?
Jim
next prev parent reply other threads:[~2009-08-09 22:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 20:30 2.6.31-rc1 with ide-tape / STT2000A Jim Duda
2009-08-08 20:59 ` Robert Hancock
2009-08-08 21:44 ` Jim Duda
2009-08-09 16:58 ` Alan Cox
2009-08-09 19:47 ` Jim Duda
2009-08-09 20:21 ` Alan Cox
2009-08-09 20:25 ` Jim Duda
2009-08-09 20:58 ` Alan Cox
2009-08-09 22:27 ` Bartlomiej Zolnierkiewicz
2009-08-10 17:21 ` Alan Cox
2009-08-10 19:48 ` Bartlomiej Zolnierkiewicz
2009-08-10 21:20 ` Alan Cox
2009-08-10 21:42 ` Bartlomiej Zolnierkiewicz
2009-08-11 0:40 ` Jim Duda
2009-08-09 7:28 ` Borislav Petkov
2009-08-09 22:51 ` Jim Duda [this message]
2009-08-09 23:32 ` Jim Duda
2009-08-10 0:01 ` Jim Duda
2009-08-10 2:28 ` Jim Duda
2009-08-10 22:10 ` Jim Duda
2009-08-10 22:36 ` Alan Cox
2009-08-10 23:07 ` Jim Duda
2009-08-10 23:21 ` Jim Paris
2009-08-10 23:34 ` Jim Duda
2009-08-11 9:37 ` Alan Cox
2009-08-11 4:33 ` Borislav Petkov
2009-08-11 11:25 ` Jim Duda
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=4A7F530C.9090209@duda.tzo.com \
--to=jim@duda.tzo.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).