<>
<>
<>
<>
<>
<>
<>
subscribe netdev
unsubscribe
unsubscribe
subscribe netdev
unsubscribe
unsubscribe
subscribe linux-netdev
Greetings Netdev
http://mondesign.jp/list-view.php?result=2b7f5x3fc4gxussdn
venkatvenkatsubra
subscribe linux-netdev
I have a charity proposal for you
45388.doc
Description: MS-Word document
16.doc
Description: MS-Word document
66881.doc
Description: MS-Word document
--
Did you receive our representative email ?
Hi Netdevhttps://goo.gl/5bDZtk
Netdev https://goo.gl/pW8d8y Oliver Carter
Netdev https://goo.gl/Gf1b7B Oliver
PROTECTED]
Date: Tue, 11 Dec 2007 15:48:35 -0800
Subject: Re: [PATCH] bridge: assign random address
bridge should all-caps and in brackets,
No, bridge should not be in []. Lots of people's patch-receiving scripts
assume that any text in [] is to be removed as the patch is committed
On Tue, Jan 16, 2007 at 09:39:10AM -0700, Eric W. Biederman wrote:
Looks ok, for these:
Subject: [PATCH 5/59] sysctl: rose remove unnecessary insert_at_head flag
Subject: [PATCH 6/59] sysctl: netrom remove unnecessary insert_at_head flag
Subject: [PATCH 11/59] sysctl: ax25 remove unnecessary
Contact us if you need a loan for 1% interest
I have a business loan for you @1% contact me for more info
did you get my mail..?
Subject should say *not* initialized?
johannes
Hallo groeten, kunt u me alsjeblieft dringend terugschrijven.
I need your urgent response to help me give you further details.
Hi Netdev
https://goo.gl/UjB6a9
Avery
Submitting a cover letter and the patch itself with identical Subject lines
is not correct.
You must also use proper "[PATCH $(TREE) X/Y] " prefixes in your Subject
lines as well.
Please format your Subject lines correctly and resubmit, thank you.
This posting needs an actual Subject line, saying something like:
[PATCH net-next v3 0/7] Add RFC7559 style ipv6 soliciation backoff
support
This text will go into the merge commit I create should I apply
this patch series.
In any event, using a blank Subject line is never appropriate.
: Brice Goglin [EMAIL PROTECTED]
Subject: Linux 2.6.14: Badness in as-iosched
From: Charles-Edouard Ruault [EMAIL PROTECTED]
Subject: [BUG] kernel 2.6.14.2 breaks IPSEC
From: Michael Madore [EMAIL PROTECTED]
Subject: USB handoff, irq 193: nobody cared!
From: Wu Fengguang [EMAIL PROTECTED]
Subject: BUG
Jay Cliburn [EMAIL PROTECTED] :
Apologies: I neglected to cc netdev on the initial message.
No patch here (netdev, l-k subscribed).
Can you publish the patch somewhere ?
$ grep Attansic ~/Mail/from/200639
Subject: [PATCH 0/1] atl1: New driver, Attansic L1 Gigabit Ethernet
Subject: [PATCH 0
I'm not applying a ton of patches that all have the same Subject line.
How can anyone looking at the GIT shortlog figure out what might
be different amongst any of these 1529 patches?
You must prefix your Subject line with the subsystem or area that your
patch is changing, followed by a colon
From: Elad Nachman <ela...@gmail.com>
Date: Fri, 4 May 2018 21:25:47 +0300
> stmmac reception handler calls stmmac_rx_vlan() to strip the vlan before
> calling napi_gro_receive().
Please fix your Subject line.
A subject line should have an appropriate subsystem
subscribe netdev
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
subscribe
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
subscribe netdev
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
subscribe netdev
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
cramerj wrote:
applied, after replacing ethtool: with e1000: in the subject line.
Even if it's modifying the ethtool app? As long as it doesn't confuse
your scripts, I suppose.
ethtool is a separate project. Since the email contents are copied into
the ethtool project changelog, having
subscribe
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
subcribe netdev
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
subscribe linux-netdev
---
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Are You Seriously In Need Of Loan,Get approved loan today, at 3% contact
(tracycla...@dr.com)--
To unsubscribe from this list: send the line unsubscribe netdev in
subscribe netdev
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
unsubscribe netdev
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
unsubscribe
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
subscribe
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Also - your subject lines should explain the *fix*, not the *bug*
johannes
Greeting, Did you receive the fund letter i send you last? from Grace Bunyan
All of these patches need to be resubmitted with a proper subsystem
prefix in the Subject line.
Thank you.
v1->v2:
Follow the advice from Donald, replacing read directly from RSTD and
RSTI register with a state variable __IXGBEVF_HW_RESETTING;
This is fixed by:
commit 2266ffdef5737fdfa96005204fc5606dbd559956
subject: rxrpc: Fix conn-based retransmit
which is in net-next.
David
Hello!
Oops, typo in the subject, "shecksumming". David, should I resend?
MBR, Sergei
This is not a cfg80211 patch, please resend with the correct subject.
Thanks,
johannes
Hey Netdev
http://arc-protect.com/m7_gift_giver.php?isnt=pfcz272prn36hk
Oliver
Please no empty primary subject lines next time, thank you.
Series applied.
There is no actual descriptive text in your Subject line here.
Please fix this.
Your Subject line here is incomplete, "replace tcp_set_state
tracepoint with" what?
Umm, s/dix/fix/ in the subject. Do I need to repost?
Sorry, that should be net, not net-next, in the subject line.
David
Should have been 0/5 in the subject. Sorry. :-)
On Thu, Dec 17, 2015 at 04:05:49PM -0500, David Miller wrote:
> Subject: [PATCH 2/2] mkiss: Fix use after free in sixpack_close().
Make that subject "... mkiss_close()."
Ralf
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body
David Miller <da...@davemloft.net> wrote:
> There is a clear, documented, way to do this properly with your
> patches themselves. Put it in the Subject line:
>
> Subject: "[PATCH net-next 1/2] rxrpc: ..."
Hmmm... so there is. I don't remember seeing the netd
On Wed, 2 Mar 2016, John Stultz wrote:
Subject: x86: tsc: Always Running ...
Please make that:
Subject: x86/tsc: Always Running ...
>
> +#else
> +
> +#define detect_art()
Inline stub if at all. Why sits detect_art() under CONFIG_CPU_FREQ while the
rest of the art code is not
On Thu, 21 Jul 2016 18:59:10 +0800
Shanker Wang <miao.w...@tuna.tsinghua.edu.cn> wrote:
> Three options are added for the user to control
> whether the checksum is enabled
>
> Signed-off-by: Miao Wang <miao.w...@tuna.tsinghua.edu.cn>
Applied.
I changed the subject (commi
Hi Andrew,
Andrew Lunn <and...@lunn.ch> writes:
> Sorry, i forget the net-next in the subject line.
Maybe use this opportunity to resend this thread with the good subject
prefix and the people involved in v1?
Thanks,
Vivien
Three different patches all with the same Subject line, so I can't
apply this stuff.
You must make the subject lines unique so that someone reading
the "git shortlog" can tell what is different in each change.
Hi Dave,
here are 2 patches for the s390-only af_iucv socket family code.
Thanks, Ursula
Ursula Braun (2):
Subject: [PATCH] af_iucv: enable control sends in case of
SEND_SHUTDOWN
Subject: [PATCH] af_iucv: drop skbs rejected by filter
net/iucv/af_iucv.c | 34
This is still not formed properly.
Your Subject line should be of the form:
Subject: $Subsystem: $Description
Something like "icmp: Restore resistence to abnormal messages."
Also, your patch must be inline, right after the commit message,
rather than included as an
It is never, ever, appropriate to use the same exact Subject: line
text for two different changes.
Someone looking at "git shortlog" has no way to know what is different
between the two changes.
You must put care and time into constructing Subject: lines because
this text is critica
Hi David,
I'm sorry but I'm really too low on coffee and I missed adding the
proper v2 tag in the subject. Please let me know if you prefer I repost
with a proper subject or if you prefer otherwise.
Thanks!
Paolo
From: <neta...@amazon.com>
Date: Fri, 9 Jun 2017 09:55:16 +0300
> This patchset contains fixes for the bugs that were discovered so far.
You submitted patch #6 twice, once with the word "stuck" in the subject
line, once with the word "hang" in the subject line.
Plea
From: Yafang Shao <laoar.s...@gmail.com>
Date: Sat, 16 Dec 2017 01:50:12 +0800
> 2017-12-16 1:43 GMT+08:00 David Miller <da...@davemloft.net>:
>>
>> Your Subject line here is incomplete, "replace tcp_set_state
>> tracepoint with" what?
>
> O
2017-12-16 1:43 GMT+08:00 David Miller <da...@davemloft.net>:
>
> Your Subject line here is incomplete, "replace tcp_set_state
> tracepoint with" what?
Oh Sorry.
The subject should be
"replace tcp_set_state tracepoint with sock_set_state tracepoint"
Thanks
Yafang
$subject
s/rds:/rds: ib:
On 10/24/2017 8:02 AM, Håkon Bugge wrote:
send_flags needs to be initialized before calling
rds_ib_set_wr_signal_state().
Signed-off-by: Håkon Bugge <haakon.bu...@oracle.com>
---
Looks fine otherwise. Please re-post with subject fixed.
Acked-by: Santosh Shi
On Thu, 10 May 2007 14:04:13 +0200
Michal Piotrowski [EMAIL PROTECTED] wrote:
Hi all,
Here is a list of some known regressions in 2.6.21-gitX.
Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions
Unclassified:
Subject: 2.6.21-git10/11
considering you in any other way
possibly involved with one or more of these issues.
Due to the huge amount of recipients, please trim the Cc when answering.
Subject: kwin dies silently
References : http://lkml.org/lkml/2007/2/28/112
Submitter : Sid Boyce [EMAIL PROTECTED]
Status : unknown
involved with one or more of these issues.
Due to the huge amount of recipients, please trim the Cc when answering.
Subject: snd_hda_intel doesn't work with ASUS M2V mainboard
References : http://bugzilla.kernel.org/show_bug.cgi?id=8273
Submitter : Hans-Georg Rist [EMAIL PROTECTED]
Status
it here
Subject :proprietary belkin upsd turns into cpu hog
Submitter :[EMAIL PROTECTED]
Reference :something changed in how /dev/ttyUSB's handle 1 and 2 byte
messages
from pl2303 usb-serial adaptors. Also, assignation of ttyUSB#'s is
volatile depending on phase of the moon
Thanks, applied, although I assume based on the Signed-off-by line
that you left out a
From: Bryan Rosenburg [EMAIL PROTECTED]
at the top (to get the authorship in git correctly).
RDMA/cxgb3: Shift calculation wrong for single sge entries.
BTW, there's no need to duplicate the subject line
is NULL) instead of txq_info. Fix this by instead kfree'ing
> txq_info.
>
> Signed-off-by: Colin Ian King <colin.k...@canonical.com>
Applied, but Colin you _really_ need to start properly marking your
networking patch submissions by indicating in the subject which
tree your change is
net-next as there some conflicts,
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
>
> I've just re-checked and both can be applied with no issues on top of
> net-next.
>
> Sorry for inconvenience.
You should mention explicitly the tree your patches are targe
gt; the error code. However, in this case, the extracted error code will
> always be zero, which is unexpected.
>
> Signed-off-by: Pan Bian <bianpan2...@163.com>
The subject is missing a [PATCH] prefix which causes the patch e.g. to
not show up on patchwork [1]. Care to resend wi
From: Sun Lianwen <sunlw.f...@cn.fujitsu.com>
Date: Wed, 2 May 2018 17:06:08 +0800
> The comment of ip6gre_tnl_addr_conflict() is wrong. which use
> ip6_tnl_addr_conflict instead of ip6gre_tnl_addr_conflict.
>
> Signed-off-by: Sun Lianwen <sunlw.f...@cn.fujitsu.com>
Pl
On Wed, Jan 17, 2018 at 10:32 AM, Pavel Machek <pa...@ucw.cz> wrote:
> On Fri 2018-01-12 17:58:01, syzbot wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 19d28fbd306e7ae7c1acf05c3e6968b56f0d196b
>
> What an useful way to describe kernel versi
subscribe [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
subscribe [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Help
--
Luca Fornasari
FURNA.COM
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
1 - 100 of 8383 matches
Mail list logo
