From: Mark Langsdorf <mark.langsdorf@calxeda.com>
To: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>
Cc: Jan Ceuleers <jan.ceuleers@computer.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"jgarzik@pobox.com" <jgarzik@pobox.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] ata: Fix build error in sata_highbank
Date: Fri, 28 Sep 2012 12:56:31 -0500 [thread overview]
Message-ID: <5065E4CF.9020200@calxeda.com> (raw)
In-Reply-To: <CA+icZUXTNyhO-Y7kFw7xtf8DEgb-5KZCfPxHb7miRZ4Qyov+Hw@mail.gmail.com>
On 09/28/2012 12:37 PM, Sedat Dilek wrote:
> On Fri, Sep 28, 2012 at 7:30 PM, Jan Ceuleers <jan.ceuleers@computer.org> wrote:
>> On 09/28/2012 07:23 PM, Mark Langsdorf wrote:
>>> From: Mark Langsdorf <Mark Langsdorf>
>>
>> Mark,
>>
>> This From: line is malformed: the bit between the angle brackets should
>> contain an email address.
>>
>
> Randy sent a patch to linux-next ML and pinged again on this (see [1]).
> I see no Reported-by... no S-o-b :-(.
>
> - Sedat -
>
> [1] http://marc.info/?t=134807860300006&r=1&w=2
I submitted patch immediately after he reported it and was told that
Jeff Garzik would push it up:
http://patchwork.kernel.org/patch/1460971
I'm really not sure why this isn't in linux-next already.
--Mark Langsdorf
Calxeda, Inc.
prev parent reply other threads:[~2012-09-28 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 17:23 [PATCH] ata: Fix build error in sata_highbank Mark Langsdorf
2012-09-28 17:30 ` Jan Ceuleers
2012-09-28 17:37 ` Sedat Dilek
2012-09-28 17:56 ` Mark Langsdorf [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=5065E4CF.9020200@calxeda.com \
--to=mark.langsdorf@calxeda.com \
--cc=jan.ceuleers@computer.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).