From: Richard <h.vanberkum@chello.nl>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] drivers/atm/nicstar.c: add KERN_* to printk
Date: Thu, 06 Jul 2006 01:34:00 +0000 [thread overview]
Message-ID: <44AC872B.2050007@chello.nl> (raw)
In-Reply-To: <44ABCCD6.6060101@chello.nl>
Randy.Dunlap wrote:
> On Thu, 06 Jul 2006 04:56:44 +0200 Richard wrote:
>
>> Add KERN_* to printk statements.
>>
>> Signed-off-by: Richard van Berkum <h.vanberkum at chello.nl>
>
> The content looks good to me, but I'm just scanning over them.
>
> This one does not apply cleanly for me:
>
> patch: **** malformed patch at line 30: structure.\n", i);
>
> Something split one source line into 2 lines for you. :(
>
> Fixing that one finds another one (about 15-20 or so total bad line
> splits).
>
> It also doesn't apply cleanly to 2.6.17-git24 for me. Maybe
> it applies to 2.6.17-git25? (always send patches against a
> current linus-mainline tree)
That's this tree: rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/git.git
right? Or should I download the one from kernel.org?
Richard
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2006-07-06 1:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 12:15 [KJ] [PATCH] drivers/atm/nicstar.c: add KERN_* to printk Richard
2006-07-05 16:07 ` Randy.Dunlap
2006-07-06 0:40 ` Richard
2006-07-06 1:07 ` Randy.Dunlap
2006-07-06 1:34 ` Richard [this message]
2006-07-06 1:34 ` Randy.Dunlap
2006-07-06 12:52 ` Richard
2006-07-06 15:40 ` Randy.Dunlap
2006-07-07 1:01 ` Richard
2006-07-07 3:22 ` Randy.Dunlap
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=44AC872B.2050007@chello.nl \
--to=h.vanberkum@chello.nl \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.