Re: linux-next: Tree for Jan 25 (BROKEN suspend)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello, Sedat.

On Mon, Jan 28, 2013 at 11:06:11PM +0100, Sedat Dilek wrote:
> 1. People should sent their patches concerning especially Linux-Next
> fixes not only to LKML but also to <linux-next@xxxxxxxxxxxxxxx> (if
> this is not known, pointing to James).
> 
> 2. These patches for Linux-Next should contain a "-next" in their
> subject-line (use 'git format-patch --subject-prefix="PATCH -next"
> ...').
> 
> Of course, I should have checked the MLs... but for me it was not
> clear what was the root cause (which subsystem to blame)... I had only
> some suspicions.

Yeah, there was no way for you guys to easily discover that the
problem has already been identified and fix pending.  I'll definitely
try to cc linux-next cc'd on patches which fix problems in -next.

Thanks a lot!

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux