On Wednesday 07 November 2012 07:46 PM, Arnd Bergmann wrote:
> On Wednesday 07 November 2012, Vineet Gupta wrote:
>> +static struct platform_device arc_uart##n##_dev = {\
>> + .name = "arc-uart", \
>> + .id = n,\
On Wed, Jan 16, 2013 at 08:05:28PM -0500, Jake Champlin wrote:
> Fixed a leading whitespace coding style issue.
>
> Signed-off-by: Jake Champlin
> ---
> drivers/staging/comedi/drivers/ni_tio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On Sat, Jan 12, 2013 at 02:58:35PM +0800, Axel Lin wrote:
> Signed-off-by: Axel Lin
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jan 07, 2013 at 10:28:31AM +0800, Axel Lin wrote:
> We already have enum lp8755_bucks in lp8755.h, so it looks pointless adding
> enum bucks in lp8755.c.
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Sat, Dec 29, 2012 at 09:38:50AM +0800, Axel Lin wrote:
> It looks pointless to pass max_vol to s5m8767_convert_voltage_to_sel().
> Compare selected voltage to desc->max is enough to ensure selected voltage
> is in supported range.
Applied, thanks.
--
To unsubscribe from this list: send the
On Thu, Jan 17, 2013 at 09:57:46AM +0800, Axel Lin wrote:
> The vout address for buck[1|2] can be easily calculated,
> thus remote these arrays.
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
- Original Message -
>
> I see no reason, even although I don't know why it is 46 instead of
> 40.
Ok, for "::::::255.255.255.255".
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
On Wed, 2013-01-16 at 05:11 -0800, Jacob Pan wrote:
> Intel PowerClamp driver performs synchronized idle injection across
> all online CPUs. The goal is to maintain a given package level C-state
> ratio.
>
> Compared to other throttling methods already exist in the kernel,
> such as ACPI PAD
On Thu, 2013-01-17 at 11:55 +0800, Jike Song wrote:
> On Thu, Jan 17, 2013 at 2:59 AM, David Miller wrote:
>
> >
> > When GLIBC doesn't provide it's own definition of some networking
> > macros or interfaces that the kernel provides, people include the
> > kernel header.
> >
>
> Recently I got
As Maya is going to fix the commit text,
Acked-by: Subhash Jadavani
On 1/17/2013 12:18 PM, Seungwon Jeon wrote:
On Thursday, January 17, 2013 , Ulf Hansson wrote:
On 13 January 2013 22:47, Maya Erez wrote:
-Original Message-
From: Subhash Jadavani [mailto:subha...@codeaurora.org]
On Thursday, January 17, 2013 , Ulf Hansson wrote:
> On 13 January 2013 22:47, Maya Erez wrote:
> > -Original Message-
> > From: Subhash Jadavani [mailto:subha...@codeaurora.org]
> > Sent: Saturday, January 12, 2013 9:07 AM
> > To: Maya Erez
> > Cc: linux-...@vger.kernel.org;
On Wed, Jan 16, 2013 at 10:30:45AM -0500, Alan Stern wrote:
> On Wed, 16 Jan 2013, Aaron Lu wrote:
>
> > From: Lin Ming
> >
> > When a request is added:
> > If device is suspended or is suspending and the request is not a
> > PM request, resume the device.
> >
> > When the last request
On Thu, Jan 17, 2013 at 12:43 AM, Al Cooper wrote:
> Part of the sequence is "addiu sp,sp,-8" in the delay slot after every
> call to the trace routine "_mcount" (some legacy thing where 2 arguments
> used to be pushed on the stack). The _mcount routine is expected to
> adjust the sp by +8 before
Hi Kees,
On Wed, 2013-01-16 at 18:53 -0800, Kees Cook wrote:
> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
> while now and is almost always enabled by default. As agreed during the
> Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
>
> Cc:
On Thu, Jan 17, 2013 at 3:53 AM, Kees Cook wrote:
> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
> while now and is almost always enabled by default. As agreed during the
> Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
> config MDA_CONSOLE
>
On 01/16/2013 09:08 PM, Yasuaki Ishimatsu wrote:
I thought about the method of specifying the node. But I think
this method is inconvenience. Node number is decided by OS.
So the number is changed easily.
for example:
o exmaple 1
System has 3 nodes:
node0, node1, node2
When user
t break it ;-)
>
> Hmm. It's causing a lot of engineers here a lot of trouble, since they
> all see linux-next won't boot, and haven't been paying enough attention
> to know which commit to revert:-(. Lots of lost productivity:-(
>
> Simon, the offending commit:
>
> 6d3ef6b
Hi Kukjin,
On Wed, 16 Jan 2013 21:13:00 -0800 Kukjin Kim wrote:
>
> One more, following is my preferred resolution when merge conflict happens
> between Samsung tree and arm-soc tree:
Thanks, I will use this resolution tomorrow. You will still get
notification emails just to double check.
--
Hi, Mike
I've send out the v2, which I suppose it will fix the below BUG and
perform better, please do let me know if it still cause issues on your
arm7 machine.
Regards,
Michael Wang
On 01/14/2013 05:21 PM, Mike Galbraith wrote:
> On Sat, 2013-01-12 at 11:19 +0100, Mike Galbraith wrote:
>
>>
Since schedule balance map provide the approach to get proper sd directly,
simplify the code of select_task_rq_fair() is possible.
The new code is designed to reserve most of the old logical, but get rid
of those 'for' by using the schedule balance map to locate proper sd
directly.
This patch will build schedule balance map as designed, now
cpu_sbm->sd[f][l] can directly locate the sd of cpu on level 'l'
with flag 'f' supported.
In order to quickly locate the lower sd while changing the base cpu,
the level with empty sd in map will be filled with the lower sd.
In order to get rid of the complex code in select_task_rq_fair(),
approach to directly get sd on each level with proper flag is
required.
Schedule balance map is the solution, which record the sd according
to it's flag and level.
For example, cpu_sbm->sd[wake][l] will locate the sd of cpu which
On Wed, 16 Jan 2013 14:27:30 +, Morten Rasmussen wrote:
> On Wed, Jan 16, 2013 at 06:02:21AM +, Alex Shi wrote:
>> On 01/15/2013 12:09 AM, Morten Rasmussen wrote:
>> > On Fri, Jan 11, 2013 at 07:08:45AM +, Alex Shi wrote:
>> >> On 01/10/2013 11:01 PM, Morten Rasmussen wrote:
>> >> For
v2 change log:
Fix code style issues.
Fix BUG of NULL affine_sd.
Add the support for NUMA domain.
Other small fix according to the old logical.
Provide more test data with finer granularity.
This patch set is trying to simplify the select_task_rq_fair()
On 01/11/2013 01:12 PM, Thadeu Lima de Souza Cascardo wrote:
> When doing a hotplug remove of a cxgb4 device, there are still dandling
> symlinks at /sys/class/scsi_host/hostX to the removed PCI device. The
> upper layer device may also try to send data, which may crash the
> system.
>
> The
2013년 01월 12일 15:58, Axel Lin 쓴 글:
Signed-off-by: Axel Lin
---
drivers/regulator/lp8755.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/regulator/lp8755.c b/drivers/regulator/lp8755.c
index decb3ad..8c3f3f2 100644
---
On Wed, 16 Jan 2013 22:08:21 +0800, Alex Shi wrote:
> On 01/08/2013 04:41 PM, Preeti U Murthy wrote:
>> Hi Mike,
>>
>> Thank you very much for such a clear and comprehensive explanation.
>> So when I put together the problem and the proposed solution pieces in the
>> current
>> scheduler
On Thursday 15 November 2012 06:05 PM, Arnd Bergmann wrote:
> On Thursday 15 November 2012, Vineet Gupta wrote:
>> So the primary concern here is not breaking the userspace ABI - right ?
>>
>> For syscalls I agree that we will indeed need to fix the ABI - by fixing
>> uClibc. And if uClibc doesn't
Kukjin Kim wrote:
[...]
> Hmm, updating timer patches in Samsung tree cause the merge conflicts with
> arm-soc, so for now I dropped them in my tree just now.
> And note that regarding topic branch which are including it will be
re-worked
> soon :-)
>
> Now to merge Samsung tree for linux-next
On Wed, Jan 16, 2013 at 10:30:45AM -0500, Alan Stern wrote:
> On Wed, 16 Jan 2013, Aaron Lu wrote:
>
> > From: Lin Ming
> >
> > When a request is added:
> > If device is suspended or is suspending and the request is not a
> > PM request, resume the device.
> >
> > When the last request
On Monday 12 November 2012 07:40 PM, Arnd Bergmann wrote:
> On Monday 12 November 2012, vineet.gup...@synopsys.com wrote:
>> +config ARC_DCCM_SZ
>> + int "DCCM Size in KB"
>> + default "64"
>> + depends on ARC_HAS_DCCM
>> +
>> +config ARC_DCCM_BASE
>> + hex "DCCM map
This has been tested by exchanging data with with the Contiki operating
system using a Redwire Econotag. Contiki had to be set to send uncompressed
data, and had to have a #define modified to enable reception and processing
of header-compressed packets when not set to send compressed data.
Refactor the handing of the skb's to the individual lowpan devices into a
function.
Signed-off-by: Alan Ott
---
net/ieee802154/6lowpan.c | 38 --
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git a/net/ieee802154/6lowpan.c
Handle the reception of uncompressed packets (dispatch type = IPv6).
Signed-off-by: Alan Ott
---
net/ieee802154/6lowpan.c | 41 -
1 file changed, 32 insertions(+), 9 deletions(-)
diff --git a/net/ieee802154/6lowpan.c b/net/ieee802154/6lowpan.c
index
2013/01/17 7:52, H. Peter Anvin wrote:
On 01/16/2013 01:29 PM, Andrew Morton wrote:
Yes. If SRAT support is available, all memory which enabled hotpluggable
bit are managed by ZONEMOVABLE. But performance degradation may
occur by NUMA because we can only allocate anonymous page and page-cache
On Monday 12 November 2012 07:32 PM, Arnd Bergmann wrote:
> On Monday 12 November 2012, vineet.gup...@synopsys.com wrote:
>> + /* TBD: rewrite this using I/O macros */
>> + volatile unsigned int *base = (unsigned int *)BVCI_LAT_UNIT_BASE;
>> + volatile unsigned int *lat_unit =
17.01.2013 02:51, Mark Lord пишет:
On 13-01-16 12:20 AM, Stanislav Kinsbursky wrote:
Mark, could you provide any call traces?
Call traces from where/what?
There's this one, posted earlier in the BUG report:
kernel BUG at net/sunrpc/svc_xprt.c:921!
Call Trace:
[] ? svc_recv+0xcc/0x338
Stephen Warren wrote @ Wed, 16 Jan 2013 21:11:24 +0100:
> >> +static int clk_frac_div_set_rate(struct clk_hw *hw, unsigned long rate,
> >> + unsigned long parent_rate)
> >> +{
> >> + struct tegra_clk_frac_div *divider = to_clk_frac_div(hw);
> >> + int
Kukjin Kim wrote:
>
> Stephen Rothwell wrote:
> >
> > Hi Kukjin,
> >
> Hi,
>
> > On Fri, 11 Jan 2013 15:32:06 +1100 Stephen Rothwell
>
> > wrote:
> > >
> > > Today's linux-next merge of the samsung tree got conflicts in
> > > many files with the arm-soc tree.
> > >
> > > I just dropped the
On Thu, Jan 17, 2013 at 12:27:32AM +0100, Rafael J. Wysocki wrote:
> > +static int __init acpi_csrt_init(void)
> > +{
> > + struct acpi_csrt_group *grp, *end;
> > + struct acpi_table_csrt *csrt;
> > + acpi_status status;
> > + int ret;
> > +
> > + status = acpi_get_table(ACPI_SIG_CSRT,
On Wed, 16 Jan 2013 18:49:02 -0800 "Darrick J. Wong"
wrote:
> >
> > The problem back in 2001 was that we held lock_page() across the
> > duration of page writeback, so if another thread came in and tried to
> > dirty the page, it would block on lock_page() until IO completion. I
> > can't
On Wednesday 16 January 2013 11:27 PM, Stephen Warren wrote:
On 01/16/2013 06:06 AM, Laxman Dewangan wrote:
Enable high speed serial driver for tegra platform.
Thanks, I've applied patch 1 to Tegra's for-3.9/defconfig branch and
patch 2 to Tegra's for-3.9/dt branch.
Just as an FYI, the dt
Hi all,
Changes since 20130116:
Dropped tree: samung (many conflicts)
The powerpc tree still had a build failure.
The tty tree gained conflicts against Linus' and the tty.current trees.
The staging tree gained a conflict against Linus' tree.
The char-misc tree gained a conflict against
On Wed, Jan 16, 2013 at 04:35:43PM -0800, Glauber Costa wrote:
>
> >> The superblocks only, are present by the dozens even in a small system,
> >> and I believe the whole goal of this API is to get more users to switch
> >> to it. This can easily use up a respectable bunch of megs.
> >>
> >>
On Wed, Jan 16, 2013 at 07:54:16PM -0800, Andrew Morton wrote:
> On Wed, 16 Jan 2013 18:42:46 -0800 Greg Kroah-Hartman
> wrote:
>
> > > FWIW, Andrew took my patch in mm:
> > >
> > > http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover.patch
> > >
> >
Stephen Rothwell wrote:
>
> Hi Kukjin,
>
Hi,
> On Fri, 11 Jan 2013 15:32:06 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the samsung tree got conflicts in
> > many files with the arm-soc tree.
> >
> > I just dropped the samsung tree for today. Please have a look and try
Stephen Rothwell wrote:
>
> Hi Kukjin,
>
Hi,
> On Fri, 11 Jan 2013 15:32:06 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the samsung tree got conflicts in
> > many files with the arm-soc tree.
> >
> > I just dropped the samsung tree for today. Please have a look and try
On Wed, Jan 16, 2013 at 10:51 PM, Steve French wrote:
> How did you discover this - did you have an ipv6 test case or by
> inspection or ...?
By mostly-automated inspection (i.e., with the help of a static
program analysis tool).
Nickolai.
--
To unsubscribe from this list: send the line
On 01/17/2013 09:42 AM, Tejun Heo wrote:
> Hello,
>
> Currently, on the backend side, there are two layers of abstraction.
> For each CPU and the special unbound wq-specific CPU, there's one
> global_cwq. gcwq in turn hosts two worker_pools - one for normal
> priority, the other for highpri -
Hi Kukjin,
On Fri, 11 Jan 2013 15:32:06 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the samsung tree got conflicts in
> many files with the arm-soc tree.
>
> I just dropped the samsung tree for today. Please have a look and try to
> fix this mess up, thanks.
Ping?
--
Makes sense.
How did you discover this - did you have an ipv6 test case or by
inspection or ...?
On Wed, Jan 16, 2013 at 8:36 PM, Nickolai Zeldovich
wrote:
> srcip_matches() previously had code like this:
>
> srcip_matches(..., struct sockaddr *rhs) {
> /* ... */
> struct sockaddr_in6
On Wed, 16 Jan 2013 18:42:46 -0800 Greg Kroah-Hartman
wrote:
> > FWIW, Andrew took my patch in mm:
> >
> > http://ozlabs.org/~akpm/mmots/broken-out/fb-rework-locking-to-fix-lock-ordering-on-takeover.patch
> >
> >
On Wed, 2013-01-16 at 14:22 -0500, Mike Frysinger wrote:
>
> but this is still too vague. what headers/definitions do people want to see
> simultaneously included ? changes would be needed on both sides (kernel & C
> library).
>
Hi, Mike,
Please take a look at my first email in this
> "Darrick" == Darrick J Wong writes:
>> Umm, why did you move this hunk?
Darrick> I moved it so that the integrity data are generated against the
Darrick> contents of the bounce buffer because the write paths don't
Darrick> wait for writeback to finish if the snapshotting mode is
Darrick>
Carlos O'Donell wrote:
> diff --git a/include/uapi/linux/in6.h b/include/uapi/linux/in6.h
> index f79c372..a2b16a5 100644
> --- a/include/uapi/linux/in6.h
> +++ b/include/uapi/linux/in6.h
> @@ -23,6 +23,13 @@
>
> #include
>
> +/* If a glibc-based userspace has already included in.h, then we
Actually, the code path affected by your patch is not executed in UMS mode
at all. Notice that radeon_cs_parser_fini is only called from
radeon_cs_ioctl which is a KMS-only ioctl (see radeon_kms.c).
The equivalent of the fix you are trying to do is in
a6b7e1a02b77ab8fe8775d20a88c53d8ba55482e
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Rob Landley
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Signed-off-by:
Fixed coding style issue with single line braces.
Signed-off-by: Jake Champlin
---
drivers/staging/usbip/usbip_common.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/usbip/usbip_common.c
b/drivers/staging/usbip/usbip_common.c
index 75189fe..75aa5bf
From: Carlos O'Donell
Date: Wed, 16 Jan 2013 21:15:03 -0500
> +/* If a glibc-based userspace has already included in.h, then we will not
> + * define in6_addr (nor the defines), sockaddr_in6, or ipv6_mreq. The
> + * ABI used by the kernel and by glibc match exactly. Neither the kernel
> + * nor
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Giuseppe Cavallaro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Grant Likely
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in
drivers/ipack/devices/ipoctal.c between commit 2e124b4a390c ("TTY: switch
tty_flip_buffer_push") from the tty tree and commits 7e5730d7c222
("ipack/devices/ipoctal: fix kernel bug when using pppd"),
e7e664fd688a
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Ralf Baechle
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Michal Simek
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Tim Waugh
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Dave Airlie
CC: Alan Cox
CC: "Kirill A. Shutemov"
Cc: Greg Kroah-Hartman
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Ralf Baechle
CC: Manuel Lauss
Cc: Greg Kroah-Hartman
Signed-off-by: Kees
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Bjorn Helgaas
CC: Jesse Barnes
CC: Matthew Garrett
Cc: Greg Kroah-Hartman
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Jeff Garzik
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Benjamin Herrenschmidt
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: Len Brown
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: "Michael S. Tsirkin"
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Mike Frysinger
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
Partially CC:'ing a mailing list for a subset of patches, without also
CC:'ing that list on your openning "00/xxx" email explaing what you're
doing and why is kind of pointless.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: Artem Bityutskiy
Cc: Al Viro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: Artem Bityutskiy
Cc: Al Viro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Dave Airlie
CC: Adam Jackson
Cc: Greg Kroah-Hartman
Signed-off-by: Kees
Carlos O'Donell wrote:
> diff --git a/include/uapi/linux/in6.h b/include/uapi/linux/in6.h
> index f79c372..a2b16a5 100644
> --- a/include/uapi/linux/in6.h
> +++ b/include/uapi/linux/in6.h
:
> #define IPV6_PRIORITY_14 0x0e00
> #define IPV6_PRIORITY_15 0x0f00
>
> +
>
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: Al Viro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: Stuart Swales
Cc: Russell King
Cc: Al Viro
Cc: Greg Kroah-Hartman
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: Florian Fainelli
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Dave Airlie
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: "John W. Linville"
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: Chris Mason
Cc: Al Viro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
Remove CONFIG_EXPERIMENTAL, now that every mention of it has been removed
from the tree.
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
init/Kconfig |4
1 file changed, 4 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index a966690..fb9f55b 100644
--- a/init/Kconfig
+++
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: David Howells
Cc: Al Viro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Florian Tobias Schandinat
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Florian Tobias Schandinat
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Tomi Valkeinen
CC: Florian Tobias Schandinat
Cc: Greg Kroah-Hartman
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: "J. Bruce Fields"
Cc: Al Viro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Richard Purdie
Cc: Greg Kroah-Hartman
Signed-off-by: Kees Cook
---
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: Eric Van Hensbergen
CC: Ron Minnich
CC: Latchesar Ionkov
Cc: Al Viro
Cc:
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
Cc: "Tigran A. Aivazian"
Cc: Al Viro
Cc: Greg Kroah-Hartman
Signed-off-by: Kees
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
CC: "James E.J. Bottomley"
CC: Helge Deller
Cc: Greg Kroah-Hartman
1 - 100 of 1847 matches
Mail list logo
