From: Tejun Heo <tj@kernel.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: xiaoming.wang@intel.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] proc: move the adding option Ngid to the end of proc/PID/status
Date: Fri, 24 Apr 2015 11:50:59 -0400 [thread overview]
Message-ID: <20150424155059.GE24029@htj.duckdns.org> (raw)
In-Reply-To: <20150423203226.GA1765@p183.telecom.by>
On Thu, Apr 23, 2015 at 11:32:26PM +0300, Alexey Dobriyan wrote:
> There are 2 fields before Ngid and 35+ after Ngid. So the risk is not
> the same. Potentionally, Ngid addition broke almost every parser.
I don't get how we reach completely different conclusions from the
same observation. This patch changes the offset for the 35+ fields
after Ngid in the current kernel instead of 4 something fields. How
is that better?
--
tejun
next prev parent reply other threads:[~2015-04-24 15:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 13:23 [PATCH] proc: move the adding option Ngid to the end of proc/PID/status Alexey Dobriyan
2015-04-17 14:26 ` Tejun Heo
2015-04-17 15:05 ` Alexey Dobriyan
2015-04-17 15:12 ` Tejun Heo
2015-04-21 8:19 ` Wang, Xiaoming
2015-04-21 14:00 ` Alexey Dobriyan
2015-04-21 15:11 ` Tejun Heo
2015-04-23 20:32 ` Alexey Dobriyan
2015-04-24 15:50 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-17 2:13 Wang Xiaoming
2015-04-17 2:56 ` Tejun Heo
2015-04-17 3:15 ` Wang, Xiaoming
2015-04-17 3:26 ` Tejun Heo
2015-04-17 3:37 ` Wang, Xiaoming
2015-04-17 3:42 ` Tejun Heo
2015-04-17 5:36 ` Wang, Xiaoming
2015-04-21 15:19 ` Eric W. Biederman
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=20150424155059.GE24029@htj.duckdns.org \
--to=tj@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=xiaoming.wang@intel.com \
/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