From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>,
jdike@addtoit.com, linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Re: [patch 1/3] uml-ubd-no-empty-queue
Date: Tue, 7 Sep 2004 20:04:03 +0200 [thread overview]
Message-ID: <200409072004.03343.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20040906142641.067fdeb6.akpm@osdl.org>
On Monday 06 September 2004 23:26, Andrew Morton wrote:
> Please don't use a filename like uml-ubd-no-empty-queue as the Subject:
> of your patches. Please prepare an English-language summary. See
> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
Ok, but how can I specify the filename you'll give to the patch?
It would make management between my tree and yours easier for me, if possible.
> I applied three of these - two got rejects against Linus's current
> tree.
>
> Do you have to do this
>
> -menu "SCSI support"
> +if BROKEN
> + menu "SCSI support"
>
> -config SCSI
>
> I think you'll find that
>
> menu "SCSI support"
> depends on BROKEN
>
> works OK.
If you want to add the dependency to SCSI, GENERIC_ISA_DMA and every item in
arch/um/Kconfig_scsi by hand, you're welcome, but I guess not :-).
Otherwise, please note I bracketed everything with if BROKEN....endif. If you
don't like the indent, that's not a problem.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
next prev parent reply other threads:[~2004-09-07 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 17:44 blaisorblade_spam
2004-09-06 21:26 ` Andrew Morton
2004-09-07 2:26 ` Jeff Garzik
2004-09-07 18:04 ` BlaisorBlade [this message]
2004-09-07 21:23 ` [uml-devel] " Andrew Morton
2004-09-07 9:35 ` Jens Axboe
2004-09-07 18:50 ` [uml-devel] " BlaisorBlade
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=200409072004.03343.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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®