From: Jesper Juhl <jesper.juhl@gmail.com>
To: Stephane Wirtel <stephane.wirtel@belgacom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/net/s2io.h - lvalue fix
Date: Tue, 30 Aug 2005 00:43:19 +0200 [thread overview]
Message-ID: <9a874849050829154311bd433d@mail.gmail.com> (raw)
In-Reply-To: <20050829222417.GA20292@localhost.localdomain>
On 8/30/05, Stephane Wirtel <stephane.wirtel@belgacom.net> wrote:
> Hi all ,
>
> Sorry if I don't send this patch to the maintainer of s2io, but I don't
> know who is he.
>
Hmm, neither do I. Looking in MAINTAINERS I don't see anybody, and
looking in the sources I find just a company name `Neterion'.
So, lacking an email address for a maintainer, sending your patch to
linux-kernel is the right thing to do (even if you had found a
maintainer, adding linux-kernel to Cc: would usually also be proper).
If you get no response at all from the list or maintainer, then Andrew
Morton is the head 2.6 maintainer.
> This patch is based on Kernel 2.6.13 release from the Linus tree.
>
> Is there a process to send patch to the mailing list ?
>
Check out
- Documentation/SubmittingPatches
- http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
- http://linux.yyz.us/patch-format.html
- http://www.tux.org/lkml/#s1-10
- http://www.tux.org/lkml/#s1-15
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-08-29 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 22:24 [PATCH] drivers/net/s2io.h - lvalue fix Stephane Wirtel
2005-08-29 22:43 ` Jesper Juhl [this message]
2005-08-29 23:07 ` Stephane Wirtel
2005-08-30 7:22 ` Alexey Dobriyan
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=9a874849050829154311bd433d@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stephane.wirtel@belgacom.net \
/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.