From: David Miller <davem@davemloft.net>
To: yinghai@kernel.org
Cc: rui.zhang@intel.com, yamato@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] genetlink: trigger BUG_ON if a group name is too long
Date: Wed, 20 Mar 2013 18:18:07 -0400 (EDT) [thread overview]
Message-ID: <20130320.181807.147847609140930081.davem@davemloft.net> (raw)
In-Reply-To: <CAE9FiQVJhAbvfxp152a0KbzFE1hVQZMNwdWkKnyii3HNWDBd=A@mail.gmail.com>
From: Yinghai Lu <yinghai@kernel.org>
Date: Wed, 20 Mar 2013 15:17:13 -0700
> On Wed, Mar 20, 2013 at 3:10 PM, David Miller <davem@davemloft.net> wrote:
>
>>> so bisecting will be broken?
>>
>> Good point, so I'll apply the thermal patch to my tree to minimize
>> the failure range.
>
> yes, that "second" patch should be applied before this one.
But it's too late as the first one is already commited to my public
GIT tree on kernel.org and I never rebase my tree, ever.
So this is the only option to minimize the damage at this point.
next prev parent reply other threads:[~2013-03-20 22:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 11:47 [PATCH 0/2] netlink: protection and workaround for too long mcast group name Masatake YAMATO
2013-03-19 11:47 ` [PATCH 1/2] genetlink: trigger BUG_ON if a group name is too long Masatake YAMATO
2013-03-20 16:07 ` David Miller
2013-03-20 17:32 ` Ben Hutchings
2013-03-21 7:49 ` Masatake YAMATO
2013-03-20 21:01 ` Yinghai Lu
2013-03-20 21:05 ` David Miller
2013-03-20 21:06 ` Yinghai Lu
2013-03-20 21:13 ` David Miller
2013-03-20 21:16 ` Yinghai Lu
2013-03-20 22:10 ` David Miller
2013-03-20 22:17 ` Yinghai Lu
2013-03-20 22:18 ` David Miller [this message]
2013-04-23 9:27 ` Masatake YAMATO
2013-03-19 11:47 ` [PATCH 2/2] thermal: shorten too long mcast group name Masatake YAMATO
2013-03-20 16:08 ` David Miller
2013-03-21 7:46 ` Masatake YAMATO
2013-03-21 14:53 ` David Miller
[not found] ` <20130321.190819.892238877314124764.yamato@redhat.com>
2013-03-22 3:43 ` Masatake YAMATO
2013-03-22 14:04 ` David Miller
2013-03-21 13:04 ` Thomas Graf
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=20130320.181807.147847609140930081.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=yamato@redhat.com \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).