All of lore.kernel.org
 help / color / mirror / Atom feed
From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: colibri-pxa300: use correct SD detect pin
Date: Fri, 24 Dec 2010 16:27:06 +0200	[thread overview]
Message-ID: <4D14ADBA.7070709@compulab.co.il> (raw)
In-Reply-To: <AANLkTikSK_+NcvoBxWWyaOOz6u8oLk-jMj9FzKW_mUhC@mail.gmail.com>

On 12/24/10 00:13, Bj?rn Forsman wrote:
> 2010/12/23 Marek Vasut <marek.vasut@gmail.com>:
>> On Thursday 23 December 2010 17:59:40 Bj?rn Forsman wrote:
>>> Hi Marek,
>>>
>>> 2010/12/23 Marek Vasut <marek.vasut@gmail.com>:
>>>> On Thursday 23 December 2010 16:01:02 Bj?rn Forsman wrote:
>>>>> The use of wrong SD detect pin was introduced by this commit:
>>>>>
>>>>>   ARM: pxa: Push Colibri evalboard MFP into module files
>>>>>
>>>>> This fixes it.
>>>> Ah, one more thing -- CC linux-arm-kernel (done)
>>> I didn't CC linux-arm-kernel because the patch was meant for
>>> Eric Miao's pxa-linux-2.6.git tree (devel branch). I doesn't apply
>>> to mainline.
>>>
>>> As Eric anyways uses 'git rebase' on his tree every -rc cycle
>>> I suggested that he could squash my patch into your original
>>> patch so that we get nice bisectable history.
>> No, no, no ... regarding arm patches, you always CC linux-arm-kernel.
> Ok.
>
> When the patch is not against mainline, where is appropriate
> place to say what tree it applies to? As a reply to the patch thread?

You can write the explanation in the cover letter, or
if it is just a small single patch without the cover letter,
then beneath the "---" line, but before the "diff ...."

-- 
Regards,
Igor.

  reply	other threads:[~2010-12-24 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1293116462-10189-1-git-send-email-bjorn.forsman@gmail.com>
2010-12-23 16:15 ` [PATCH] ARM: colibri-pxa300: use correct SD detect pin Marek Vasut
2010-12-23 16:59   ` Bjørn Forsman
2010-12-23 20:57     ` Marek Vasut
2010-12-23 22:13       ` Bjørn Forsman
2010-12-24 14:27         ` Igor Grinberg [this message]
2010-12-24 18:41           ` Bjørn Forsman
2011-01-15 18:15 ` Bjørn Forsman
2011-01-17 17:38   ` Eric Miao

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=4D14ADBA.7070709@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.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.