netdev - Re: [PATCH 3/3] documentation: fix wrt. headers rename

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 6 Aug 2009 13:26:17 +0400
From:	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, slapin@...fans.org,
	linux-zigbee-devel@...ts.sourceforge.net
Subject: Re: [PATCH 3/3] documentation: fix wrt. headers rename

On Wed, Aug 05, 2009 at 08:22:26PM -0700, David Miller wrote:
> From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
> Date: Wed,  5 Aug 2009 11:28:17 +0400
> 
> > Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
> 
> What are you generating these patches against?
> 
> > @@ -72,5 +72,4 @@ SoftMAC
> >  We are going to provide intermediate layer implementing IEEE 802.15.4 MAC
> >  in software. This is currently WIP.
> >  
> > -See header include/net/ieee802154/mac802154.h and several drivers in
> > -drivers/ieee802154/
> > +See header include/net/mac802154.h and several drivers in drivers/ieee802154/.
> 
> In net-2.6, and in Linus's tree as well, that first sentence quoted has
> a typo, "implementing" is misspelled, but in whatever you're patching
> against the misspelling is fixed.
> 
> Looking at your pull request:
> 
> --------------------
> The following changes since commit db71789c01ae7b641f83c5aa64e7df25122f4b28:
>   David S. Miller (1):
>         xfrm6: Fix xfrm6_policy.c build when SYSCTL disabled.
> --------------------
> 
> You're submitting these for net-next-2.6?  Didn't we just go back and
> forth about trimming this patch series down to only pure bug fixes so
> that they could go into net-2.6?  Given that, why are you generating
> this stuff against net-next-2.6?

Damn. It seems I missed the difference between net-next-2.6 and net-2.6.

BTW: how should I differentiate my poll requests for net-next-2.6 and
for net-2.6 ?

-- 
With best wishes
Dmitry

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html