From: "adam radford" <aradford@gmail.com>
To: "Gabriele Gorla" <gorlik@yahoo.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Patch submission question [not in the FAQ]
Date: Thu, 6 Dec 2007 13:37:28 -0800 [thread overview]
Message-ID: <b1bc6a000712061337o189b96bal45c0b7b5b7d47568@mail.gmail.com> (raw)
In-Reply-To: <602863.12913.qm@web53712.mail.re2.yahoo.com>
On Dec 5, 2007 3:36 AM, Gabriele Gorla <gorlik@yahoo.com> wrote:
> Hello,
> I have submitted a patch for the 3x-xxxx driver on
> alpha several months ago to both the driver maintainer
> and the linux-scsi mailing list.
> I have read all the FAQ and I tried to stick to the
> instructions to the letter.
> However the patch has been completely ignored. No
> reply, no comment, no flames, absolutely nothing...
>
> the original email submission is at the end of the
> email.
>
> could anyone please explain what I am doing wrong?
>
> thanks,
> GG
Gabriele,
I ignored your patch because:
1. I do not believe you have the 3w-xxxx driver running on an
alpha SMP system.
2. I removed the bitfields from the 3w-xxxx driver but I have
yet to add full big endian support due to lack of demand. I have
such a patch for this driver (which already includes the unpacking
of the wait_queue_head_t variable) but I have not submitted it to
the main-line kernel. The in-kernel 3w-xxxx driver is still missing
the byte-swaps.
The 3w-9xxx (9000 series 3ware driver) has full big endian support.
3. Your patch was garbled.
Is this an official request for big endian support for the 3w-xxxx driver or
are you looking for anybody who has a packed 'wait_queue_head_t' and
submitting a patch to fix it?
-Adam
next prev parent reply other threads:[~2007-12-06 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 11:36 Gabriele Gorla
2007-12-05 12:36 ` WANG Cong
2007-12-06 15:01 ` Jan Engelhardt
2007-12-06 21:37 ` adam radford [this message]
2007-12-09 12:57 ` Geert Uytterhoeven
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=b1bc6a000712061337o189b96bal45c0b7b5b7d47568@mail.gmail.com \
--to=aradford@gmail.com \
--cc=gorlik@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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
all inboxes | Powered by JetHome®