Hello.
Eric, to remind, you already reviewed these changes and acked
them in May. They were dropped because they conflicted with Al's
readdir rework in vfs.git, I rediffed this series.
Note: I belive this series is fine in any case, but this is also
preparation for while_each_thread() fixes.
On 11/17/13 12:27, Max Filippov wrote:
> On Sat, Nov 16, 2013 at 3:31 AM, Stephen Boyd wrote:
>> The 32 bit sched_clock interface now supports 64 bits. Upgrade
>> to the 64 bit function to allow us to remove the 32 bit
>> registration interface.
>>
>> Signed-off-by: Stephen Boyd
>> ---
>>
>>
> Hi Markus,
>
> Yes, I noticed when I merged it into my watchdog-next branch.
>
> Reminds me ... v3 had a whitespace problem. I don't recall if you fixed
> that in v4. If you didn't, that might be a better reason to send v5.
That's still there, unfortunately. Trailing space on the first
Keystone code is big endian compatible,
so mark it as one that supports big endian.
Note this patch just allows to select Big endian build
for ARCH_KEYSTONE, but it does not enable BE by default.
Signed-off-by: Taras Kondratiuk
---
Based on Linus' master tip (b4789b8).
Tested on Keystone2 EVM.
These tables are all immutable, make them const to save 4416 bytes of RAM.
size arch/arm/mach-exynos/pmu.o
textdata bss
8484420 4 // before
5264 4 4 // after
Signed-off-by: Daniel Kurtz
---
arch/arm/mach-exynos/pmu.c | 14 +++---
On 11/20/2013 9:55 AM, Thomas Gleixner wrote:
On Wed, 20 Nov 2013, Arjan van de Ven wrote:
On 11/20/2013 9:23 AM, Thomas Gleixner wrote:
On Wed, 20 Nov 2013, Arjan van de Ven wrote:
On 11/20/2013 8:04 AM, Peter Zijlstra wrote:
This does not fully preseve existing behaviour in that the
The restore functions do not modify the passed in struct sleep_save,
so that parameter can be const.
This allows us to pass in const struct. This allows us to use const
structs sleep_save to define system registers that will always be
restored to a constant value.
Signed-off-by: Daniel Kurtz
On 11/20/13 03:13, Vinayak Kale wrote:
> This patch adds an accessor function for IRQ_PER_CPU flag.
> The accessor function is useful to dertermine whether an IRQ is percpu or not.
>
> Signed-off-by: Vinayak Kale
> ---
This looks like a copy of Chris Smith's patch. Shouldn't Chris be the
author
Hi Andy,
Thanks for the patch.
On 11/20/2013 06:31 AM, Andy Shevchenko wrote:
> Instead of custom implementation of the SFI GPIO API let's use one provided by
> gpiolib.
>
> Signed-off-by: Andy Shevchenko
Acked-by: David Cohen
> ---
> arch/x86/include/asm/intel-mid.h | 1
On 11/20/2013 09:56 AM, Steven Rostedt wrote:
> On Wed, 20 Nov 2013 12:36:00 -0500
> "Frank Ch. Eigler" wrote:
>
>> Hi -
>>
Does this new blacklist cover enough that the kernel now survives a
broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms?
>>>
>>> That's generally
> FL_FILP_PRIVATE locks are no longer tied to a particular PID, and are
instead
> inheritable by child processes. Report a l_pid of '-1' for these sorts of
locks
> since the pid is somewhat meaningless for them.
Hmm, I suppose in the case of a process that acquires a private lock, forks
(passing
-Original Message-
From: Venkat Venkatsubra
Sent: Tuesday, November 19, 2013 5:33 PM
To: Honggang LI; Josh Hunt
Cc: David Miller; jjo...@suse.com; LKML; net...@vger.kernel.org
Subject: RE: [PATCH] rds: Error on offset mismatch if not loopback
We now have lot more information than we
On 20/11/2013 18:04, Peter Zijlstra wrote:
> The only valid use of preempt_enable_no_resched() is if the very next
> line is schedule() or if we know preemption cannot actually be enabled
> by that statement due to known more preempt_count 'refs'.
The reason I used the no resched version is that
On Wed, Nov 20, 2013 at 10:41:54PM +0530, Chinmay V S wrote:
> On Wed, Nov 20, 2013 at 9:25 PM, J. Bruce Fields wrote:
> > Some SSD's are also claim the ability to flush the cache on power loss:
> >
> >
> >
I neglected to fetch before sending this, so I missed the last zswap
patch. I'll update the patch and send v2 shortly.
On Wed, Nov 20, 2013 at 12:36 PM, Dan Streetman wrote:
> Currently, zswap is writeback cache; stored pages are not sent
> to swap disk, and when zswap wants to evict old
On Wednesday, November 20, 2013 06:54:34 PM Bartlomiej Zolnierkiewicz wrote:
>
> Hi Krzysztof,
>
> On Wednesday, November 20, 2013 03:12:11 PM Krzysztof Kozlowski wrote:
> > MAX14577 chip is a multi-function device which includes MUIC,
> > charger and voltage regulator. The driver is located in
On Wed, Nov 20, 2013 at 05:28:50PM +, Vinayak Kale wrote:
> In Will's existing code, I think he was taking care of 'no IRQ' case
> by comparing pmu_device->num_resources. Do you think this is not
> enough and we must enforce the check after each platform_get_irq()?
> Existing driver code
Hi,
commit c368e5fc2a190923b786f2de3e79430ea3566a25 (regulator: fixed: get
rid of {get|list}_voltage()) regresses any MMC host controller which
uses fixed regulator for functionality.
Note that mmc core uses regulator_list_voltage() to setup OCR mask and
that has a check for missing
This is loader specific code which can load bzImage and set it up for
64bit entry. This does not take care of 32bit entry or real mode entry
yet.
Signed-off-by: Vivek Goyal
---
arch/x86/include/asm/kexec-bzimage.h | 12 +
arch/x86/include/asm/kexec.h | 26 +++
The patch from commit 7cb2ef56e6a8b7b368b2e883a0a47d02fed66911 can
cause dereference of a dangling pointer if split_huge_page runs during
PageHuge() if there are updates to the tail_page->private field.
Also it is repeating compound_head twice for hugetlbfs and it is
running
On 17:31 Wed 20 Nov , boris brezillon wrote:
> On 20/11/2013 16:02, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >On 14:37 Wed 28 Aug , Boris BREZILLON wrote:
> >>Add a new at91rm9200ek_mmc board (based on at91rm9200ek board) which enables
> >>mmc0/slot0.
> >no for multiple dts
> >
> >this
Currently we don't clobber page_tail->first_page during
split_huge_page, so compound_trans_head can be set to compound_head
without adverse effects, and this mostly optimizes away a smp_rmb.
It looks worthwhile to keep around the implementation that doesn't
relay on page_tail->first_page not to
Changes since v2:
1) optimize away a few more locked ops in the get_page/put_page
hugetlbfs and slab paths (see 3/8 and 4/8).
3/8 is the least trivial addition to the series as we now are
running PageSlab and PageHeadHuge on random page structure without
holding any reference count
On Wed, 20 Nov 2013 12:36:00 -0500
"Frank Ch. Eigler" wrote:
> Hi -
>
> > > Does this new blacklist cover enough that the kernel now survives a
> > > broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms?
> >
> > That's generally the purpose of the annotations - if it doesn't then
get_page_foll is more optimal and is always safe to use under the PT
lock. More so for hugetlbfs as there's no risk of race conditions with
split_huge_page regardless of the PT lock.
Reviewed-by: Khalid Aziz
Signed-off-by: Andrea Arcangeli
---
mm/hugetlb.c | 2 +-
1 file changed, 1
No actual need of it. So keep it internal.
Signed-off-by: Andrea Arcangeli
---
mm/hugetlb.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index 9b8a14b..133ea72 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -743,7 +743,6 @@ int PageHeadHuge(struct page
On Wed, 20 Nov 2013, Arjan van de Ven wrote:
> On 11/20/2013 9:23 AM, Thomas Gleixner wrote:
> > On Wed, 20 Nov 2013, Arjan van de Ven wrote:
> >
> > > On 11/20/2013 8:04 AM, Peter Zijlstra wrote:
> > > > This does not fully preseve existing behaviour in that the generic
> > > > idle cycle
We don't actually need a reference on the head page in the slab and
hugetlbfs paths, as long as we add a smp_rmb() which should be faster
than get_page_unless_zero.
Signed-off-by: Andrea Arcangeli
---
mm/swap.c | 140 ++
1 file
Hi Krzysztof,
On Wednesday, November 20, 2013 03:12:11 PM Krzysztof Kozlowski wrote:
> MAX14577 chip is a multi-function device which includes MUIC,
> charger and voltage regulator. The driver is located in drivers/mfd.
>
> This patch adds regulator driver for MAX14577 chip. There are two
>
From: Andrew Morton
Signed-off-by: Andrew Morton
Signed-off-by: Andrea Arcangeli
---
mm/hugetlb.c | 12 ++--
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index f03e068..9b8a14b 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -724,15
Previously do_kimage_alloc() will allocate a kimage structure, copy
segment list from user space and then do the segment list sanity verification.
Break down this function in 3 parts. do_kimage_alloc_init() to do actual
allocation and basic initialization of kimage structure.
From: Andrew Morton
Tweak it so save a tab stop, make code layout slightly less nutty.
Signed-off-by: Andrew Morton
Signed-off-by: Andrea Arcangeli
---
mm/swap.c | 254 +++---
1 file changed, 125 insertions(+), 129 deletions(-)
diff
This patch implements the in kernel kexec functionality. It implements a
new system call kexec_file_load. I think parameter list of this system
call will change as I have not done the kernel image signature handling
yet. I have been told that I might have to pass the detached signature
and size as
On Wed, Nov 20, 2013 at 12:33 PM, Vladimir Murzin wrote:
> Hi Dan!
>
> On Wed, Nov 20, 2013 at 11:38:42AM -0500, Dan Streetman wrote:
>> The "compressor" and "enabled" params are currently hidden,
>> this changes them to read-only, so userspace can tell if
>> zswap is enabled or not and see what
On Tue, Nov 19, 2013 at 03:09:18PM +0100, Daniel Lezcano wrote:
> On 11/07/2013 10:01 AM, Daniel Lezcano wrote:
> >The Inter Processor Interrupt is used on ARM to tell another processor to do
> >a specific action. This is mainly used to emulate a timer interrupt on an
> >idle
> >cpu, force a cpu
This patch adds support for loading a kexec on panic (kdump) kernel usning
new system call.
Signed-off-by: Vivek Goyal
---
arch/x86/include/asm/crash.h |9 +
arch/x86/include/asm/kexec.h | 17 +
arch/x86/kernel/crash.c| 585
We detected a login attempt on your email account with valid login details from
-
Location: Napoli, Italy
IP Address:62.98.81.251
Date: Tue Nov 19, 2013
Time: 11:16 CEST
This is an unrecognized location/device.
Please follow the instructions below by carefully
On Wed, Nov 20, 2013 at 05:42:11PM +, Al Viro wrote:
> [Apologies for delay; I'd spent the last day hunting down something that
> turned out to be a VM leak completely unrelated to this stuff - it's
> present in mainline, for starters. Unreliable reproducers make for fun
> bisects ;-/
On Wed, 2013-11-20 at 08:18 +0100, Antti Miettinen wrote:
> On 20.11.2013 02:04, Andrew Morton wrote:
> > On Fri, 15 Nov 2013 19:14:22 +0200 (EET) Antti P Miettinen
> > wrote:
> >
> > > Use ARRAY_SIZE instead of sizeof to get proper max for label
> > > length.
> > >
> > > Signed-off-by: Antti
On Tue, Nov 19, 2013 at 9:40 PM, David Miller wrote:
> From: fre...@asix.com.tw
> Date: Wed, 20 Nov 2013 10:11:36 +0800
>
>> From: Freddy Xin
>>
>> This patch adds a workaroud to solve Suspend/Resume issue that AX88772B turns
>> off its Ethernet PHY power in the case that REMOTE_WAKEUP feature
[Apologies for delay; I'd spent the last day hunting down something that
turned out to be a VM leak completely unrelated to this stuff - it's
present in mainline, for starters. Unreliable reproducers make for fun
bisects ;-/ Anyway, by now I'm absolutely sure that this is a VM bug and
not
Currently, zswap is writeback cache; stored pages are not sent
to swap disk, and when zswap wants to evict old pages it must
first write them back to swap cache/disk manually. This avoids
swap out disk I/O up front, but only moves that disk I/O to
the writeback case (for pages that are evicted),
Hi -
> > Does this new blacklist cover enough that the kernel now survives a
> > broadly wildcarded perf-probe, e.g. over e.g. all of its kallsyms?
>
> That's generally the purpose of the annotations - if it doesn't then
> that's a bug.
AFAIK, no kernel since kprobes was introduced has ever
Hello,
Sorry about the delay.
On Fri, Nov 08, 2013 at 04:15:23PM +0800, Chen Gang wrote:
> After simplify, the related operation, environments and output are:
>
> [root@gchenlinux tmp]# df -Th | grep cgroup
> tmpfs tmpfs1001M 0 1001M 0%
>
Hi Dan!
On Wed, Nov 20, 2013 at 11:38:42AM -0500, Dan Streetman wrote:
> The "compressor" and "enabled" params are currently hidden,
> this changes them to read-only, so userspace can tell if
> zswap is enabled or not and see what compressor is in use.
Could you elaborate more why this pice of
On 11/21/2013 12:27 AM, Greg Kroah-Hartman wrote:
On Wed, Nov 20, 2013 at 05:26:57PM +0800, Peng Tao wrote:
On Wed, Nov 20, 2013 at 2:37 AM, Greg Kroah-Hartman
wrote:
On Tue, Nov 19, 2013 at 09:23:43PM +0800, Peng Tao wrote:
From: Amir Shehata
The core of the issue is that the selftest
On Wed 20-11-13 18:21:23, Vladimir Murzin wrote:
> On Tue, Nov 19, 2013 at 02:40:07PM +0100, Michal Hocko wrote:
> Hi Michal
> > On Tue 19-11-13 14:14:00, Michal Hocko wrote:
> > [...]
> > > We have basically ended up with 3 options AFAIR:
> > > 1) allow memcg approach (memcg.oom_control) on the
On 11/20/2013 10:24 AM, Tejun Heo wrote:
> On Wed, Nov 06, 2013 at 07:14:44PM +0800, Hong Zhiguo wrote:
>> From: Hong Zhiguo
>>
>> Update of blkg_stat and blkg_rwstat may happen in bh context.
>> While u64_stats_fetch_retry is only preempt_disable on 32bit
>> UP system. This is not enough to
Hi Marc,
On Wed, Nov 20, 2013 at 6:44 PM, Marc Zyngier wrote:
> [dropped patc...@apm.com]
>
> Vinayak,
>
> Please keep reviewers on CC, as it makes easier to track the changes.
Sure, will do.
>
> On 20/11/13 11:13, Vinayak Kale wrote:
>> Add support for irq registration when pmu interrupt is
Hi David
On Wed, Nov 20, 2013 at 12:02:20AM -0800, David Rientjes wrote:
> On Tue, 19 Nov 2013, Michal Hocko wrote:
>
> > > We have basically ended up with 3 options AFAIR:
> > > 1) allow memcg approach (memcg.oom_control) on the root level
> > >for both OOM notification and
On 11/20/2013 9:23 AM, Thomas Gleixner wrote:
On Wed, 20 Nov 2013, Arjan van de Ven wrote:
On 11/20/2013 8:04 AM, Peter Zijlstra wrote:
This does not fully preseve existing behaviour in that the generic
idle cycle function calls into the normal cpuidle governed idle
routines and should thus
On Wed, Nov 06, 2013 at 07:14:44PM +0800, Hong Zhiguo wrote:
> From: Hong Zhiguo
>
> Update of blkg_stat and blkg_rwstat may happen in bh context.
> While u64_stats_fetch_retry is only preempt_disable on 32bit
> UP system. This is not enough to avoid preemption by bh and
> may read strange 64
On Tue, Nov 19, 2013 at 02:40:07PM +0100, Michal Hocko wrote:
Hi Michal
> On Tue 19-11-13 14:14:00, Michal Hocko wrote:
> [...]
> > We have basically ended up with 3 options AFAIR:
> > 1) allow memcg approach (memcg.oom_control) on the root level
> >for both OOM notification and
On 17:14 Wed 20 Nov , boris brezillon wrote:
> On 20/11/2013 15:59, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >On 13:06 Wed 28 Aug , Boris BREZILLON wrote:
> >>Add slot0 of mmc0 pinctrl pins definitions:
> >> - detect pin
> >> - write protect pin
> >> - enable slot0 pin: this pin is
On Wed, 20 Nov 2013 17:34:53 +0100
Peter Zijlstra wrote:
> On Wed, Nov 20, 2013 at 05:04:50PM +0100, Peter Zijlstra wrote:
> > I ran head-first into intel_powerclamp and acpi_pad yesterday --
> > afaict they try and do pretty much the same thing but both had
> > competing sets of bugs and
On Wed, Nov 20, 2013 at 9:25 PM, J. Bruce Fields wrote:
> Some SSD's are also claim the ability to flush the cache on power loss:
>
>
> http://www.intel.com/content/www/us/en/solid-state-drives/ssd-320-series-power-loss-data-protection-brief.html
>
> Which should in theory let them
Hello,
Sorry about the long delay. Except for the several nits that I
mentioned, things generally look good to me.
Thanks a lot for your patience.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Wed, Nov 20, 2013 at 7:22 AM, Michal Hocko wrote:
> On Wed 20-11-13 00:02:20, David Rientjes wrote:
>> On Tue, 19 Nov 2013, Michal Hocko wrote:
>>
>> > > We have basically ended up with 3 options AFAIR:
>> > > 1) allow memcg approach (memcg.oom_control) on the root level
>> > >
On 20/11/2013 16:59, boris brezillon wrote:
On 20/11/2013 15:56, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 13:02 Wed 28 Aug , Boris BREZILLON wrote:
Add spi0 cs pinctrl pins definitions.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/at91rm9200.dtsi | 20
On Wed, Nov 20, 2013 at 08:14:21AM -0800, Eric Dumazet wrote:
> On Wed, 2013-11-20 at 18:06 +0200, Michael S. Tsirkin wrote:
>
> > Hmm some kind of disconnect here.
> > I got you rmanagement about bufferbloat.
> >
> > What I am saying is that maybe we should drop packets more
> > aggressively:
On Wed, Nov 20, 2013 at 08:40:49AM -0800, Arjan van de Ven wrote:
> On 11/20/2013 8:04 AM, Peter Zijlstra wrote:
> >This does not fully preseve existing behaviour in that the generic
> >idle cycle function calls into the normal cpuidle governed idle
> >routines and should thus respect things like
On Wed, 2013-11-20 at 10:37 +0100, leroy christophe wrote:
> Scott,
>
> The patch "Convert some mftb/mftbu into
> mfspr" (beb2dc0a7a84be003ce54e98b95d65cc66e6e536) breaks startup on
> MPC885.
>
> The CPU traps (SoftwareEmulation trap) at sched_clock() when trying to
> read TBU with mfspr.
>
>
On Wed, Nov 20, 2013 at 8:44 AM, Miklos Szeredi wrote:
> On Wed, Nov 20, 2013 at 5:39 PM, Andy Lutomirski wrote:
>> On Wed, Nov 20, 2013 at 5:01 AM, Miklos Szeredi wrote:
>>> From: Miklos Szeredi
>>>
>>> If flags contain RENAME_EXCHANGE then exchange source and destination files.
>>> There's
On Wed, Nov 20, 2013 at 12:12 AM, Thomas Hellstrom
wrote:
> On 11/19/2013 11:51 PM, Andy Lutomirski wrote:
>>
>> On 11/19/2013 12:06 PM, Thomas Hellstrom wrote:
>>>
>>> Hi!
>>>
>>> Before going any further with this I'd like to check whether this is an
>>> acceptable way to go.
>>> Background:
On 11/19/2013 10:49 AM, Andi Kleen wrote:
>
> We already have all the code. Why not just use it?
>
We're talking user space here, which has different requirement (COW,
memory protection, ...) which means it is not really the same code. You
can't take a page fault while patching the kernel.
>
Add a wrapper around assign_type that does this instead of duplicating
this check in two places. This also fixes a minor wart in the code where
we continue referring to the struct flock after converting it to struct
file_lock.
Signed-off-by: Jeff Layton
---
fs/locks.c | 61
This function currently removes leases in addition to flock locks, so
the name is misleading. Rename it to locks_remove_filp to indicate that
it removes locks that are associated with a particular filp.
Signed-off-by: Jeff Layton
---
fs/file_table.c| 2 +-
fs/locks.c | 2 +-
This patchset is the second posting of this set. Here's an overview of
the changes:
The inheritance semantics have been changed to be much more like BSD
(aka flock()) locks. With this change, what we basically have are a
hybrid of BSD and POSIX locks. They conflict with "classic" POSIX locks
but
FL_FILP_PRIVATE locks are no longer tied to a particular PID, and are
instead inheritable by child processes. Report a l_pid of '-1' for
these sorts of locks since the pid is somewhat meaningless for them.
Signed-off-by: Jeff Layton
---
fs/locks.c | 4 ++--
1 file changed, 2 insertions(+), 2
On Wed, Nov 20, 2013 at 5:01 AM, Miklos Szeredi wrote:
> From: Miklos Szeredi
>
> If flags contain RENAME_EXCHANGE then exchange source and destination files.
> There's no restriction on the type of the files; e.g. a directory can be
> exchanged with a symlink.
What happens if both
On 11/20/2013 07:03 AM, Hiroshi Doyu wrote:
> Thierry Reding wrote @ Wed, 20 Nov 2013 14:14:48
> +0100:
(Yes, what Thierry said)
>
>>> Does the above mean the following?
>>>
>>> int of_iommu_attach(struct device *dev)
>>> {
>>> int i;
>>> struct of_phandle_args args;
>>>
>>>
On 11/20/2013 8:33 AM, Peter Zijlstra wrote:
On Wed, Nov 20, 2013 at 08:24:47AM -0800, Arjan van de Ven wrote:
On 11/20/2013 2:58 AM, Peter Zijlstra wrote:
So pretty silly actually; you cannot do a store (any store) in between
monitor and mwait.
you can
just not to the cacheline you are
People are starting to grow their own idle implementations in various
disgusting ways. Collapse the lot and use the generic idle code to
provide a proper idle cycle implementation.
This does not fully preseve existing behaviour in that the generic
idle cycle function calls into the normal cpuidle
Currently local_bh_disable() is out-of-line for no apparent reason.
So inline it to save a few cycles on call/return nonsense, the
function body is a single add on x86 (a few loads and store extra on
load/store archs).
Also expose two new local_bh functions:
__local_bh_{dis,en}able_ip(unsigned
Currently all _bh_ lock functions do two preempt_count operations:
local_bh_disable();
preempt_disable();
and for the unlock:
preempt_enable_no_resched();
local_bh_enable();
Since its a waste of perfectly good cycles to modify the same variable
twice when you can do it in one go; use
On Wed, Nov 20, 2013 at 08:24:47AM -0800, Arjan van de Ven wrote:
> On 11/20/2013 2:58 AM, Peter Zijlstra wrote:
> >So pretty silly actually; you cannot do a store (any store) in between
> >monitor and mwait.
>
> you can
> just not to the cacheline you are watching (or things that alias with
With various drivers wanting to inject idle time; we get people
calling idle routines outside of the idle loop proper.
Therefore we need to be extra careful about not missing
TIF_NEED_RESCHED -> PREEMPT_NEED_RESCHED propagations.
While looking at this, I also realized there's a small window in
Discourage drivers/modules to be creative with preemption.
Sadly all is implemented in macros and inline so if they want to do
evil they still can, but at least try and discourage some.
Cc: Rusty Russell
Cc: Arjan van de Ven
Cc: l...@kernel.org
Cc: r...@rjwysocki.net
Cc: Eliezer Tamir
Cc:
301 - 400 of 1243 matches
Mail list logo
