From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-08-04
Date: Mon, 04 Aug 2008 14:58:55 -0700 (PDT) [thread overview]
Message-ID: <20080804.145855.230579810.davem@davemloft.net> (raw)
In-Reply-To: <1217886123.7819.23.camel@californication>
From: Marcel Holtmann <marcel@holtmann.org>
Date: Mon, 04 Aug 2008 23:42:03 +0200
> Hi John,
>
> > > > Luis R. Rodriguez (4):
> > > > list.h: Add list_splice_tail() and list_splice_tail_init()
> > > > list.h: add list_cut_position()
> > >
> > > have these two changes got reviewed on LKML? I don't see any ACKs for it
> > > in the commit message.
> >
> > Hmmm...no. I thought the original patches had been copied to
> > linux-kernel, but it looks like that is not the case.
> >
> > The original patches are archived here:
> >
> > http://marc.info/?l=linux-wireless&m=121783421908441&w=2
> >
> > http://marc.info/?l=linux-wireless&m=121783422008445&w=2
> >
> > What problems do you see with them?
>
> I don't see a problem with these patches, but they should at least be
> reviewed on LKML once. Changes to core kernel infrastructure should not
> be merged silently via subsystem trees without any kind of ACKs.
Right.
next prev parent reply other threads:[~2008-08-04 21:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 19:37 John W. Linville
2008-08-04 20:38 ` Marcel Holtmann
2008-08-04 20:45 ` John W. Linville
2008-08-04 21:42 ` Marcel Holtmann
2008-08-04 21:54 ` John W. Linville
2008-08-04 22:37 ` Marcel Holtmann
2008-08-04 22:45 ` Luis R. Rodriguez
2008-08-04 23:38 ` Justin Mattock
2008-08-04 21:58 ` David Miller [this message]
2008-08-04 22:01 ` David Miller
2008-08-05 2:17 ` John W. Linville
2008-08-05 3:04 ` Pavel Roskin
2008-08-05 8:28 ` David Miller
2008-08-05 13:28 ` Stephen Rothwell
2008-08-05 14:05 ` John W. Linville
2008-08-05 15:30 ` Stephen Rothwell
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=20080804.145855.230579810.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.org \
--cc=netdev@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
Powered by JetHome