From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: Ned Forrester <nforrester-/d+BM93fTQY@public.gmane.org>
Cc: spi-devel
<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
merrij3-IL7dBOYR4Vg@public.gmane.org,
Stephen Street
<stephen-nl6u4wocdmy51APUEpUfAkEOCMrvLtNR@public.gmane.org>
Subject: Re: [Patch 0/1] spi: Fix pxa2xx_spi.c chip select sequence error
Date: Wed, 20 Feb 2008 14:48:45 -0800 [thread overview]
Message-ID: <200802201448.46106.david-b@pacbell.net> (raw)
In-Reply-To: <47B90B11.6000601-/d+BM93fTQY@public.gmane.org>
> David:
>
> Is there a defined procedure for distributing patches the can be
> applied to different kernel versions, when they won't apply directly?
A couple of them. One is to just cc the "stable" list,
possibly with a note about merge issues. Another is to
leave the issue up to other folk who support back-rev
kernels, which isn't quite as useful.
>
> David:
>
> Can I assume that you or someone up the chain will go through the
> motions of applying this patch to 2.6.25 and showing that it compiles?
> I really don't expect any trouble with that.
Yes.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2008-02-20 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 4:35 [Patch 0/1] spi: Fix pxa2xx_spi.c chip select sequence error Ned Forrester
[not found] ` <47B90B11.6000601-/d+BM93fTQY@public.gmane.org>
2008-02-18 22:21 ` J. Scott Merritt
[not found] ` <20080218172128.6fd1522c.merrij3-IL7dBOYR4Vg@public.gmane.org>
2008-02-18 23:03 ` Ned Forrester
[not found] ` <47BA0ED9.5040501-/d+BM93fTQY@public.gmane.org>
2008-02-20 18:26 ` Ned Forrester
2008-02-20 22:48 ` David Brownell [this message]
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=200802201448.46106.david-b@pacbell.net \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=merrij3-IL7dBOYR4Vg@public.gmane.org \
--cc=nforrester-/d+BM93fTQY@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=stephen-nl6u4wocdmy51APUEpUfAkEOCMrvLtNR@public.gmane.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.