As some of you have noticed I've barely merged any patches or answered emails in the past few months for personal reasons and I'm just digging myself out from the resulting skyhigh mountain of backlog I'm burried under. Many of the patches didn't get the Linus mandated soak time in linux-next much will missed the 3.5 merge window. I've worked through some of the backlog earlier this week as usual sorting everything into fixes and small bits that can go to Linus as after 3.5-rc1 will be released and the bigger, more dangerous bits that will need to soak until the merge window for 3.6 opens. This was harder by some folks resubmitting their patches, sometimes even several times unchanged from earlier submissions. I also still have thousands of unread emails. If you haven't received an answer yet, please don't take it personal. Patch submissions that were sent to linux-mips@xxxxxxxxxxxxxx will automatically have been sucked up by patchworks. This is _the_ reason why you really want to cc the mailing list on all patch submissions. Feel free to cc to my personal address though. As long as a patch is still listed in patchwork there is no need to resubmit. But if you resubmit, please mark older versions of your patches as superseded. All this is reuired is a patchwork account. If you don't have one already creating one at http://patchwork.linux-mips.org/ will only take a minute. A single account can also handle submissions from multiple email addresses, for example from your work and a gmail address. Having patchwork know which email addresses belong to the same person helps when searching for submissions from a single person that is is going to make my life a tad easier. One last request - take care of your password for patchwork. It seems there is no facility for a user to change his own password, so only a patchwork sysadmin can replace it when it's lost. Ralf
