netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: spereira@tusc.com.au
Cc: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>,
	acme@ghostprotocols.net, ak@muc.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, pereira.shaun@gmail.com,
	"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: 32 bit (socket layer) ioctl emulation for 64 bit kernels
Date: Thu, 19 Jan 2006 01:57:37 +0100	[thread overview]
Message-ID: <200601190157.38277.arnd@arndb.de> (raw)
In-Reply-To: <1137567396.14130.2.camel@spereira05.tusc.com.au>

Am Wednesday 18 January 2006 07:56 schrieb Shaun Pereira:
>  Assuming you are happy with the state of the patches, is there anyway
> for me to know if they will become a part of the next release?

I don't see any more technical problems with your patches. You still need
to proper patch description and Signed-off-by: line like it is described
in Documentation/SubmittingPatches.
You can add an 'Acked-by: Arnd Bergmann <arnd@arndb.de>' line to the four
patches you posted last if you like.

> Usually submitted/reviewed patches to netdev does not not always
> guarantee they will be acccepted/signed-off.
> Any advice would be useful

I'm not that familiar with the process for non-driver patches for netdev
(nor for device drivers as it seems ;-)), but my understanding is that you 
should address those to Jeff Garzik as well, asking for inclusion in the
netdev-2.6 git tree in your introductory '[PATCH 0/4]' mail.

Since the official merge window for 2.6.16 is now over (2.6.16-rc1 has been
released), it may have to wait for 2.6.17 to become part of the mainline
kernel, that probably depends on Jeffs judgement.

I would think it can still go in since it is a bug fix for the execution of
32 bit programs using x25 ioctls, but it's clearly not my decision ;-).

	Arnd <><

  reply	other threads:[~2006-01-19  0:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12  6:02 [PATCH 2/4 - 2.6.15]net: 32 bit (socket layer) ioctl emulation for 64 bit kernels Shaun Pereira
2006-01-12 19:24 ` Arnd Bergmann
2006-01-13  3:14   ` Shaun Pereira
2006-01-13 11:46     ` Arnd Bergmann
2006-01-16  5:59       ` Shaun Pereira
2006-01-16  6:41         ` YOSHIFUJI Hideaki / 吉藤英明
     [not found]           ` <200601161043.31742.arnd@arndb.de>
2006-01-16 23:11             ` [PATCH 1/4 - 2.6.15 ]net : " Shaun Pereira
2006-01-16 23:11             ` [PATCH 2/4 - 2.6.15]net: " Shaun Pereira
2006-01-16 23:12             ` [PATCH 3/4 -2.6.15]:x25: " Shaun Pereira
2006-01-17  0:15               ` Arnd Bergmann
2006-01-17  4:20                 ` [PATCH 3/4 -2.6.15- RESEND]:x25: " Shaun Pereira
2006-01-18  6:56                 ` Shaun Pereira
2006-01-19  0:57                   ` Arnd Bergmann [this message]
2006-01-19  1:05                     ` David S. Miller
2006-01-16 23:12             ` [PATCH 4/4]x25: " Shaun Pereira
2006-01-16  9:39         ` Arnd Bergmann

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=200601190157.38277.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=acme@ghostprotocols.net \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pereira.shaun@gmail.com \
    --cc=spereira@tusc.com.au \
    --cc=yoshfuji@linux-ipv6.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).