From: Derek Simkowiak <derek@webtuner.tv>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc@vger.kernel.org, romain.izard.pro@gmail.com
Subject: Re: Seeking correct git repo
Date: Thu, 26 Jun 2014 11:27:11 -0700 [thread overview]
Message-ID: <53AC65FF.1010301@webtuner.tv> (raw)
In-Reply-To: <cc919527-97e4-46ef-9952-3ceeaea97193@email.android.com>
Uffe,
Thank you for your prompt response.
>///you should either send a ping or resend the patch./
I am happy to copy'n'paste the patch from the URL (below) and resend it
to this list.
However, my understanding is that the email header "from " or "From:"
lines are used to track authorship in the CONTRIBUTORS file. I don't
want to receive credit for Romain's work by re-sending his patch. Is
there a way for me to re-submit the patch on Romain's behalf? (I have
also CC:'d Romain, so he can resubmit it directly.)
I can verify that this patch is necessary to make Jedec 5.0 hardware
work. It should get into linux-stable as soon as possible, so that
Linux can support newer eMMC hardware.
Thank You,
Derek
On 06/26/2014 02:35 AM, Ulf Hansson wrote:
> On 25 juni 2014 21:28:57 CEST, Derek Simkowiak<derek@webtuner.tv> wrote:
>> Hello,
>> A while ago, Romain wrote a small eMMC 5.0 patch that Ulf ack'd:
>>
>> http://comments.gmane.org/gmane.linux.kernel.mmc/23795
>>
>> I need this patch for my hardware. But I don't see this patch in Linux
>>
>> stable (even though there are more recent patches from Seungwon Jeon in
>>
>> there), and I don't see it at the MMC repo either:
>>
>> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git
>>
>> # Where's the patch? I checked all branches...
>>
>> $ git branch -a
>> * master
>> remotes/origin/HEAD -> origin/master
>> remotes/origin/master
>> remotes/origin/mmc-next
>> remotes/origin/mmc-updates-for-3.16-rc1-merged
>>
>>
>> Can you please tell me, what is the repo and branch where this patch
>> was
>> submitted? The only reference I have to this patch is the email
>> archive
>> at the URL above.
> Seems like it was missed. That could happen, then you should either send a ping or resend the patch.
>
> Kind regards
> Uffe
>> Thank You,
>> Derek
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message tomajordomo@vger.kernel.org
>> More majordomo info athttp://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-26 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 19:28 Seeking correct git repo Derek Simkowiak
2014-06-26 1:08 ` Hsin-Hsiang Tseng
2014-06-26 9:35 ` Ulf Hansson
2014-06-26 18:27 ` Derek Simkowiak [this message]
2014-06-27 8:51 ` [PATCH v2] mmc: Allow forward compatibility for e⋅MMC Romain Izard
2014-07-08 12:26 ` Ulf Hansson
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=53AC65FF.1010301@webtuner.tv \
--to=derek@webtuner.tv \
--cc=linux-mmc@vger.kernel.org \
--cc=romain.izard.pro@gmail.com \
--cc=ulf.hansson@linaro.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 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).